System and methods for session management

ABSTRACT

A network architecture and methods of managing packet data unit (PDU) sessions in a network are provided. The methods include PDU session establishment procedures, PDU session modification procedures, PDU session state transfer procedures, PDU session release procedures, and user equipment (UE) handover procedures.

CROSS REFERENCE TO RELATED APPLICATIONS

This application a continuation of U.S. non-Provisional patentapplication Ser. No. 15/862,194 entitled “System and Methods for SessionManagement” filed Jan. 4, 2018, which is related to U.S. ProvisionalPatent Application Ser. No. 62/444,251 entitled “System and Methods forSession Management” filed Jan. 9, 2017, to U.S. Provisional PatentApplication Ser. No. 62/448,239 entitled “System and Methods for SessionManagement” filed Jan. 19, 2017, to U.S. Provisional Patent ApplicationSer. No. 62/455,412 entitled “System and Methods for Session Management”filed Feb. 6, 2017, to U.S. Provisional Patent Application Ser. No.62/460,533 entitled “System and Methods for Session Management” filedFeb. 17, 2017, to U.S. Provisional Patent Application Ser. No.62/472,720 entitled “System and Methods for Session Management” filedMar. 17, 2017, to U.S. Provisional Patent Application Ser. No.62/492,045 entitled “System and Methods for Session Management” filedApr. 28, 2017, to U.S. Provisional Patent Application Ser. No.62/503,117 entitled “System and Methods for Session Management” filedMay 8, 2017, and U.S. Provisional Patent Application Ser. No. 62/521,922entitled “System and Methods for Session Management” filed Jun. 19, 2017the contents of which are incorporated herein by reference, inclusive ofall filed appendices.

FIELD OF THE INVENTION

The present invention pertains to the field of network communications,and in particular to system and methods for packet data unit (PDU)session-related management.

BACKGROUND

When a user equipment (UE) initiates a new data session in a fifthgeneration (5G) network, the UE attaches (i.e., connects, or registers)to the network. A session management function of the network willoversee connection management tasks. Furthermore, when a UE is alreadyattached to a network, the session management function may overseechanges to UE's network connection. Current session managementprocedures include signaling overhead and connection time issues.

This background information is provided to reveal information believedby the applicant to be of possible relevance to the present invention.No admission is necessarily intended, nor should be construed, that anyof the preceding information constitutes prior art against the presentinvention.

SUMMARY

An object of embodiments of the present invention is to provide a systemand methods for session management of a communications network.

In accordance with embodiments of the present invention, there isprovided a method of releasing a packet data unit (PDU) session. Themethod comprises determining to trigger a PDU session release, sending aN4 Session Release Request message to a User Plane Function (UPF),receiving a N4 Session Release Response message from the UPF, sending aN11 Request with PDU Session Release Command to an access and mobilityfunction (AMF), receiving a N11 Response with PDU Session ReleaseAcknowledgement from the AMF, and sending a N11 message to the AMF.

In accordance with embodiments of the present invention, there is alsoprovided a handover method comprising receiving a N2 Path Switch Requestfrom a Target Radio Access Network (T-RAN), sending a N11 Message to aSession Management Function (SMF), receiving N11 Message Acknowledgmentfrom the SMF, and sending a N2 Path Switch Request Acknowledgment to theT-RAN.

BRIEF DESCRIPTION OF THE FIGURES

Further features and advantages of the present invention will becomeapparent from the following detailed description, taken in combinationwith the appended drawings, in which:

FIG. 1 illustrates, in a block diagram, a computing system that may beused for implementing devices and methods disclosed herein;

FIG. 2A illustrates, in a component diagram, an example of acommunication network architecture;

FIG. 2B illustrates, in a component diagram, an example of a non-roamingnext generation (NG) (such as 5G mobile wireless networks) architecture,in point-to-point reference point representation;

FIG. 2C is a block diagram illustrating a service-based view of a systemarchitecture of a 5G Core Network;

FIG. 3 illustrates, in a message flow diagram, an example of methods ofattaching and re-attaching a UE to a data network;

FIG. 4 illustrates, in a component diagram, an example of a Session-IDLEstate model;

FIG. 5 illustrates, in a component diagram, an example of aSession-ACTIVE state model;

FIG. 6A illustrates, in a state diagram, an example of a sessionmanagement state model in a UE;

FIG. 6B illustrates, in a state diagram, an example of a sessionmanagement state model in a SMF;

FIG. 6C illustrates, in a component diagram, an example of a sessionmanagement state model for multiple PDU sessions;

FIG. 7 illustrates, in a message flow diagram, an example of a sessionestablishment procedure, in accordance with an embodiment of the presentinvention;

FIG. 8 illustrates, in a message flow diagram, an example of the SMF-AMFUE mobility information subscription procedure, in accordance with anembodiment of the session establishment procedure;

FIG. 9 illustrates, in a message flow diagram, an example of the SMF-UDMUE context update procedure, in accordance with an embodiment of thesession establishment procedure;

FIG. 10 illustrates, in a message flow diagram, an example of a AMF-UDMUE context update procedure, in accordance with an embodiment of thesession establishment procedure;

FIG. 11 illustrates, in a message flow diagram, an example of a SMF-PCFsession update procedure, in accordance with an embodiment of thesession establishment procedure;

FIG. 12 illustrates, in a flowchart, an example of a method ofestablishing a session, in accordance with the session establishmentprocedure;

FIG. 13 illustrates, in a message flow diagram, an example of a sessionmodification procedure, in accordance with an embodiment of the presentinvention;

FIG. 14 illustrates, in a flowchart, an example of a method modifying asession, in accordance with the session modification procedure;

FIG. 15 illustrates, in a message flow diagram, an example of a sessionrelease procedure, in accordance with an embodiment of the presentinvention;

FIG. 16 illustrates, in a flowchart, an example of a method of releasinga session, in accordance with the session release procedure;

FIG. 17 illustrates, in a flowchart, another example of a method ofreleasing a session, in accordance with the session release procedure;

FIG. 18 illustrates, in a message flow diagram, an example of a PDUsession connection state transition procedure, in accordance with anembodiment of the present invention;

FIG. 19 illustrates, in a flowchart, an example of a method ofperforming a state transition, in accordance with the PDU sessionconnection state transition procedure;

FIG. 20 illustrates, in a message flow diagram, an example of an RRCsuspend procedure, in accordance with an embodiment of the presentinvention;

FIG. 21 illustrates, in a flowchart, an example of a method oftransitioning a session state, in accordance with the RRC suspendprocedure;

FIG. 22 illustrates, in a flowchart, another example of a method oftransitioning a session state, in accordance with the RRC suspendprocedure;

FIG. 23 illustrates, in a message flow diagram, an example of a RRCresume procedure, in accordance with an embodiment of the presentinvention;

FIG. 24 illustrates, in a flowchart, an example of a method oftransitioning a session state, in accordance with the RRC resumeprocedure;

FIG. 25 illustrates, in a flowchart, an example of a method oftransitioning a session state, in accordance with the RRC resumeprocedure;

FIG. 26 illustrates, in a message flow diagram, an example of anindividual PDU Session-IDLE state transition procedure, in accordancewith an embodiment of the present invention;

FIG. 27 illustrates, in a flowchart, an example of a method oftransitioning a session state, in accordance with the individual PDUSession-IDLE state transition procedure;

FIG. 28 illustrates, in a flowchart, another example of a method oftransitioning a session state, in accordance with the individual PDUSession-IDLE state transition procedure;

FIG. 29 illustrates, in a message flow diagram, another example of a PDUSession-ACTIVE state transition procedure, in accordance with anembodiment of the present invention;

FIG. 30 illustrates, in a message flow diagram, an example of a PDUSession-ACTIVE state transition procedure, in accordance with anembodiment of the present invention;

FIG. 31 illustrates, in a flowchart, an example of a method ofperforming a Session-ACTIVE state transition, in accordance with the PDUSession-ACTIVE state transition procedure;

FIG. 32 illustrates, in a message flow diagram, an example of a PDUSession-ACTIVE state transition procedure, in accordance with anembodiment of the present invention;

FIG. 33 illustrates, in a flowchart, an example of a method oftransitioning a session, in accordance with the PDU Session-ACTIVE statetransition procedure;

FIG. 34 illustrates, in a component diagram, an example of an “UpdateUE's CN State” service procedure;

FIG. 35 illustrates, in a component diagram, an example of a “PDUSession Modification” service procedure;

FIG. 36 illustrates, in a component diagram, an example of a “Get UEPolicies” service procedure;

FIG. 37 illustrates, in a component diagram, an example of an “Update UEContext” service procedure;

FIG. 38 illustrates, in a component diagram, an example of an “Update UEContext” service procedure; and

FIG. 39 is a message flow diagram illustrating an example method of anembodiment of the present invention.

FIG. 40 is a message flow diagram illustrating an example method of anembodiment of the present invention.

FIG. 41 illustrates, in a message flow diagram, an example of a N2Release and PDU session deactivation procedure, in accordance with anembodiment of the present invention.

FIG. 42 illustrates, in a flowchart, an example of a method of releasingN2 connection and deactivating PDU sessions, in accordance with the N2Release and PDU session deactivation procedure.

FIG. 43 illustrates, in a flowchart, another example of a method ofdeactivating a PDU session, in accordance with the PDU sessiondeactivation procedure.

FIG. 44 illustrates, in a message flow diagram, another example of a PDUsession deactivation procedure, in accordance with an embodiment of thepresent invention.

FIG. 45 illustrates, in a flowchart, an example of a method ofdeactivating a PDU session, in accordance with the PDU sessiondeactivation procedure of FIG. 44.

FIG. 46 illustrates, in a flowchart, another example of a method ofdeactivating a PDU session, in accordance with the PDU sessiondeactivation procedure of FIG. 44.

FIG. 47 illustrates, in a message flow diagram, another example of asession-ACTIVE state transition procedure, in accordance with anembodiment of the present invention.

FIG. 48 illustrates, in a flowchart, an example of a method oftransitioning a session, in accordance with the session-ACTIVE statetransition procedure of FIG. 47.

FIG. 49 illustrates, in a flowchart, another example of a method oftransitioning a session, in accordance with the session-ACTIVE statetransition procedure of FIG. 47.

FIG. 50 illustrates, in a message flow diagram, an example of a servicerequest procedure, in accordance with an embodiment of the presentinvention.

FIG. 51 illustrates, in a message flow diagram, an example of a servicerequest procedure (5100), in accordance with an embodiment of thepresent invention.

FIG. 52A illustrates, in a state diagram, an example of a sessionmanagement state model in a UE, in accordance with an embodiment of thepresent invention.

FIG. 52B illustrates, in a state diagram, an example of a sessionmanagement state model in an AMF and/or a SMF, in accordance with anembodiment of the present invention.

FIG. 53 illustrates, in a message flow diagram, an example of a Xn basedinter NG RAN handover procedure without UPF relocation, in accordancewith an embodiment of the present invention.

FIG. 54 illustrates, in a flowchart, an example of a method of handingover a UE from a source RAN to a target RAN, in accordance with the Xnbased inter NG RAN handover procedure of FIG. 53.

FIG. 55 illustrates, in a flowchart, another example of a method ofhanding over a UE from a source RAN to a target RAN, in accordance withthe Xn based inter NG RAN handover procedure of FIG. 53.

FIG. 56 illustrates, in a message flow diagram, an example of a Xn basedinter NG RAN handover procedure with user plan function relocation, inaccordance with an embodiment of the present invention.

FIG. 57 illustrates, in a message flow diagram, an example of a N3reconnection procedure triggered by UL data, in accordance with anembodiment of the present invention.

FIG. 58 illustrates, in a message flow diagram, an example of a N3reconnection procedure triggered by DL data, in accordance with anembodiment of the present invention.

FIG. 59 illustrates, in a message flow diagram, an example of a N2Release and PDU Session deactivation procedure, in accordance withembodiments of the present invention.

FIG. 60 illustrates, in a message flow diagram, another example of a N2Release and PDU Session deactivation procedure, in accordance withembodiments of the present invention.

FIG. 61 illustrates, in a message flow diagram, an example of a PDUsession release procedure triggered by the UE, PCF, or the SMF, inaccordance with embodiments of the present invention.

FIG. 62 illustrates, in a message flow diagram, another example of a PDUsession release procedure triggered by the UE or the SMF, in accordancewith embodiments of the present invention.

FIG. 63 illustrates, in a message call diagram, an example of a Xn basedinter NG (R)AN handover procedure without user plane function relocationand with session deactivation, in accordance with embodiments of thepresent invention

FIG. 64 illustrates, in a message flow diagram, an example of aUE-triggered Service Request procedure, in accordance with embodimentsof the present invention.

FIG. 65 illustrates, in a message flow diagram, an example of a latepath switch procedure triggered by DL data without a UPF relocation, inaccordance with embodiments of the present invention.

FIG. 66 illustrates, in a message flow diagram, an example of a latepath switch procedure triggered by UL data with UPF reselection, inaccordance with embodiments of the present invention.

FIG. 67 illustrates, in a message flow diagram, an example of a latepath switch procedure triggered by DL data with UPF reselection, inaccordance with embodiments of the present invention.

FIG. 68 illustrates, in a message flow diagram, an example of a UPFreselection procedure, in accordance with embodiments of the presentinvention.

FIG. 69 illustrates, in a message flow diagram, an example of aprocedure for a UE context release in an AN, in accordance withembodiments of the present invention.

FIG. 70 illustrates, in a message flow diagram, an example of aprocedure for a UE or CN requested PDU session release for Non-Roamingand Roaming with Local Breakout, in accordance with embodiments of thepresent invention.

FIG. 71 illustrates, in a message flow diagram, an example of aprocedure for a UE or CN requested PDU session release for Home-routedRoaming, in accordance with embodiments of the present invention.

FIG. 72 illustrates, in a message flow diagram, an example of a Xn basedinter NG (R)AN handover procedure without user plane functionrelocation, in accordance with embodiments of the present invention.

FIG. 73 illustrates, in a message flow diagram, an example of a Xn basedinter NG (R)AN handover procedure with user plan function relocation, inaccordance with embodiments of the present invention.

FIG. 74 illustrates, in a message flow diagram, an example of a UEtriggered Service Request procedure, in accordance with embodiments ofthe present invention.

FIG. 75 illustrates, in a message flow diagram, an example of a UEtriggered Service Request procedure in CM-CONNECTED state, in accordancewith embodiments of the present invention.

FIG. 76 illustrates in a message flow diagram, an example of a NetworkTriggered Service Request procedure, in accordance with embodiments ofthe present invention.

FIG. 77 illustrates, in a message flow diagram, an example of a UEtriggered Service Request procedure in CM-CONNECTED state, in accordancewith embodiments of the present invention.

FIG. 78 illustrates, in a message flow diagram, an example of an IntraAMF, inter NG-RAN node handover procedure without Xn interface, inaccordance with embodiments of the present invention.

FIG. 79 illustrates, in a message flow diagram, an example of N2 Releaseprocedure, which is also known as UE Context Release in AN procedure, inaccordance with embodiments of the present invention.

FIG. 80 is a message flow diagram illustrating an example of UE ornetwork requested PDU session release for non-roaming and roaming withlocal breakout, in accordance with embodiments of the present invention.

FIG. 81 is a message flow diagram illustrating an example procedure forUE context release in the AN, in accordance with embodiments of thepresent invention.

FIGS. 82A and 82B are a message flow diagram illustrating an example UEtriggered Service Request procedure, in accordance with embodiments ofthe present invention.

FIGS. 83A and 83B are a message flow diagram illustrating an example UEtriggered Service Request procedure in CM-CONNECTED state, in accordancewith embodiments of the present invention.

It will be noted that throughout the appended drawings, like featuresare identified by like reference numerals.

DETAILED DESCRIPTION

Embodiments of the present invention are directed towards sessionmanagement procedures for a communications network.

As used herein, a “network” or “communication network” may servicevarious devices including but is not necessarily limited to, wirelessdevices. Such a network may include a radio access portion and abackhaul portion. The network may further comprise various virtualizedcomponents. A primary example of such a network is a 5G network, whichis reconfigurable and capable of network slicing.

Network slicing relates to the ability of a network, such as a 5Gcommunication network accessible by wireless devices, to providemultiple logical network slices on demand, with each network sliceoperating as a substantially separate network for different marketscenarios which demand diverse requirements. The capabilities andoperating parameters of each network slice may be customized to theservice requirements. Configuration of the network slices may be basedon software defined networking, network function virtualization andnetwork orchestration.

One use of network slicing is in the core network. Through the use ofnetwork slicing, different service providers can have distinct corenetworks that run on the same physical set of network and computingresources. This can also be used to create a virtual network dedicatedto particular types of network traffic. It should be understood thatthis discussion is not intended to exclude the application of networkslicing to the radio access edge of the radio access network (RAN),which may use specific functionality to support multiple network slicesor partitioning of resources for different network slices. In order toprovide performance guarantees, the network slices may be isolated fromeach other so that one slice does not negatively affect the otherslices. The isolation is not restricted to different types of services,but also allows the operator to deploy multiple instances of the samenetwork partition.

Network slicing allows the instantiation of separate network slicesrespectively directed toward different network services. This allowsdifferent types of traffic to be isolated from each other by assigningeach traffic type to a different slice. Each slice can havecharacteristics tailored to the needs of the traffic flow it carries.Such needs may include different packet processing requirements,different service requirements, and different quality of service (QoS)requirements. Different network slices corresponding to differentallocations of pooled resources may offer different services todifferent customers, or groups of customers. The different services maybe supported by different network slices (a network slice may beconsidered as a type of customized virtual network), where the differentnetwork slices (i.e., different customized virtual networks) aresubstantially separate from one another from the customer's point ofview though they may share common physical network resources. The pooledresources may be commercial off-the-shelf hardware components capable ofconfiguration through virtualization approaches, such as NFV, in orderto support various network functionalities for supporting the operationsof the network slices.

Session management functionality in a network is responsible for thesetup of Internet protocol (IP) or non-IP traffic connectivity for auser equipment (UE), as well as the management of the user plane forthat connectivity. Network functions within the next generation (NG)control plane may have service based interfaces for services that can beused by authorized network functions.

FIG. 1 is a block diagram illustrating a computing system 100 that maybe used for implementing devices and methods disclosed herein. Specificdevices may utilize all of the components shown or only a subset of thecomponents, and levels of integration may vary from device to device.Furthermore, a device may contain multiple instances of a component,such as multiple processing units, processors, memories, transmitters,receivers, etc. The computing system 100 includes a processing unit 102.The processing unit 102 includes a central processing unit (CPU) 104,memory 106, and may further include a mass storage device 108, a videoadapter 110, and an I/O interface 112 connected to a bus 114.

The bus 114 may be one or more of any type of several bus architecturesincluding a memory bus or memory controller, a peripheral bus, or avideo bus. The CPU 104 may comprise any type of electronic dataprocessor. The memory 106 may comprise any type of non-transitory systemmemory such as static random access memory (SRAM), dynamic random accessmemory (DRAM), synchronous DRAM (SDRAM), read-only memory (ROM), or acombination thereof. The memory 106 may include ROM for use at boot-up,and DRAM for program and data storage for use while executing programs.

The mass storage 108 may comprise any type of non-transitory storagedevice configured to store data, programs, and other information and tomake the data, programs, and other information accessible via the bus114. The mass storage 108 may comprise, for example, one or more of asolid state drive, hard disk drive, a magnetic disk drive, or an opticaldisk drive.

The video adapter 110 and the I/O interface 112 provide interfaces tocouple external input and output devices to the processing unit 102. Asillustrated, examples of input and output devices include a display 116coupled to the video adapter 110 and a mouse/keyboard/printer 118coupled to the I/O interface 112. Other devices may be coupled to theprocessing unit 102, and additional or fewer interface cards may beutilized. For example, a serial interface such as universal serial bus(USB) (not shown) may be used to provide an interface for an externaldevice.

The processing unit 102 may also include one or more network interfaces120, which may comprise wired links, such as an Ethernet cable, and/orwireless links to access nodes or different networks. The networkinterfaces 120 allow the processing unit 102 to communicate with remoteunits via the networks. For example, the network interfaces 120 mayprovide wireless communication via one or more transmitters/transmitantennas and one or more receivers/receive antennas. The processing unit102 may be coupled to a local-area network 122 or a wide-area networkfor data processing and communications with remote devices, such asother processing units, the Internet, or remote storage facilities.

FIG. 2A illustrates, in a component diagram, an example of acommunication network architecture 200. The communication networkarchitecture 200 comprises a user equipment (UE) 202, an access network(AN) 204, a core network (CN) 206 and a data network (DN) 208. Oneexample of an AN 204 is a radio access network (RAN). The term (R)AN isused in this description to designate that either an AN and/or a RAN mayapply. The UE 202 communicates with a DN 208 via the (R)AN 204 and CN206. Message packet data units (PDUs) between the UE 202 and DN 208 passthrough the (R)AN 204 and CN 206. A DN 208 may be a public networkoperator, a private data network, such as local area data work (LADN),an intra-operator data network, or any other type of data network.

In an uplink (UL) direction, user plane (UP) PDUs pass from the UE 202to the (R)AN 204 via a communication link. The (R)AN 204 forward the UPPDUs to the CN 206 that then forwards the UP PDUs to the DN 208. In adownlink (DL) direction, DL PDUs pass from the DN 208 to the CN 206 thatthen forwards the DL PDUs to the (R)AN 204 that then forwards the DLPDUs to the UE 202. CP functionality on the CN 206 configures UPfunctions on the CN 206 to provide traffic handling functionality for asession. One or more UP functions per session may be activated andconfigured by the CP functionality for a given UP scenario.

The connections between the components of the communication networkarchitecture 200 may be suitable for any communication channel. For nextgeneration (NG) architectures, the connection between the (R)AN 204 andthe CP of the CN 206 may be via an NG2 interface. The connection betweenthe (R)AN 204 and the UP of the CN 206 may be via an NG3 interface. Theconnection between the UP of the CN 206 and the DN 208 may be via an NG6interface.

FIG. 2B illustrates, in a component diagram, an example of a non-roamingNG (such as 5G mobile wireless networks) architecture 210, inpoint-to-point reference point representation. The non-roaming NGarchitecture 210 comprises the UE 202, the (R)AN 204, the CN 206, anapplication function (AF) 250 that is outside the CN 206 and the DN 208.The CN 206 comprises a UP function (UPF) module 212 and CP functions.The CP functions include an authentication server function (AUSF) 214, aunified data management (UDM) function 216, an access and mobilitymanagement function (AMF) 218, a session management function (SMF) 220,and a policy control function (PCF) 222. The AMF 218 manages thetermination of signalling interfaces NG1 and NG2, the forwarding ofsignalling messages from the UE 202 and the (R)AN 204 to the SMF 220,and the management of mobility and security procedures for the UE 202.The SMF manages the UP connection establishment between the UE 202 andthe DN 208. The PCF 222 provides policies to different network functionsto handle a UE's session, such as QoS, mobility management, sessionmanagement and charging policies. The UDM 216 provides storagemanagement for network information and user information, and securitymeasures to protect the data. The AUSF 214 provides security functions,such as authenticating the users and users' requests, and providingsecurity keys for encrypting data transmitted over interfaces. The AF224 may be any application server outside the 3GPP network, whichprovides control information between external applications and the CN206. For example, an IMS server may be an AF 224. The UPF 212 providesuser plane functions, such as mapping IP packets to QoS flows,forwarding packets, traffic measurement and preparing and sendingreports. The (R)AN 204 provides an air interface connection for the UE202, and forwards packets between the UE 202 and CN UPF 212.

The components of the CN 206 in the non-roaming NG architecture 210 maybe implemented as software modules on one or more servers. FIG. 2Billustrates one example of possible interfaces between some of thecomponents. Table 1 shows the communication interfaces used by some ofthe components in FIG. 2B.

TABLE 1 Interfaces used by some components of a non-roaming NGarchitecture Component Interface Component UE 202 NG1 AMF 218 (R)AN 204NG2 AMF 218 (R)AN 204 NG3 UPF 212 UPF 212 NG4 SMF 220 PCF 222 NG5 AF 224UPF 212 NG6 DN 208 SMF 220 NG7 PCF 220 AMF 218 NG8 UDM 216 UDM 216 NG10SMF 220 AMF 218 NG11 SMF 220 AUSF 214 NG12 AMF 218 AUSF 214 NG13 UDM 216AMF 218 NG14 AMF 218 AMF 218 NG15 PCF 222

FIG. 2C illustrates a service-based architecture 226 for a 5G or NextGeneration Core Network (5GCN/NGCN/NCN). This illustration depictslogical connections between nodes and functions, and its illustratedconnections should not be interpreted as direct physical connections. UE202 forms a radio access network connection with a (Radio) AccessNetwork ((R)AN) node 228 (which may, for example, be an gNodeB (gNB)),which is connected to a CN User Plane (UP) Function (UPF) 212 such as aUP Gateway over a network interface providing a defined interface suchas an N3 interface. UPF 212 provides a logical connection to a DataNetwork (DN) 208 over a network interface such as an N6 interface. Theradio access network connection between the UE 202 and the (R)AN node226 may be referred to as a Data Radio Bearer (DRB).

DN 208 may be a data network used to provide an operator service, or itmay be outside the scope of the standardization of the Third GenerationPartnership Project (3GPP), such as the Internet, a network used toprovide third party service, and in some embodiments DN 208 mayrepresent an Edge Computing network or resource, such as a Mobile EdgeComputing (MEC) network.

UE 202 also connects to the Access and Mobility Management Function(AMF) 218 through a logical N1 connection (although the physical path ofthe connection is not direct). The AMF 218 is responsible forauthentication and authorization of access requests, as well as mobilitymanagement functions. The AMF 218 may perform other roles and functionsas defined by the 3GPP Technical Specification (TS) 23.501. In a servicebased view, AMF 218 can communicate with other core network controlplane functions through a service based interface denoted as Namf.

The Session Management Function (SMF) 220 is a network function that isresponsible for the allocation and management of IP addresses that areassigned to an ED as well as the selection of a UPF 212 (or a particularinstance of a UPF 212) for traffic associated with a particular sessionof UE 202. It will be appreciated that there will typically be multipleSMFs 220 in the network 226, each of which may be associated with arespective group of UEs 202, (R)AN nodes 2282 or UPFs 212. The SMF 220can communicate with other core network functions, in a service basedview, through a service based interface denoted as Nsmf. The SMF 220 mayalso connect to a UPF 212 through a logical interface such as networkinterface N4.

The Authentication Server Function (AUSF) 214, provides authenticationservices to other network functions over a service based Nausfinterface.

A Network Exposure Function (NEF) 230 can be deployed in the network toallow servers, functions and other entities such as those outside atrusted domain to have exposure to services and capabilities within thenetwork. In one such example, an NEF 230 can act much like a proxybetween an application server outside the illustrated network andnetwork functions such as the Policy Control Function (PCF) 222, the SMF220, the UDM 216, and the AMF 218, so that the external applicationserver can provide information that may be of use in the setup of theparameters associated with a data session. The NEF 230 can communicatewith other network functions through a service based Nnef networkinterface. The NEF 230 may also have an interface to non-3GPP functions.

A Network Repository Function (NRF) 232, provides network servicediscovery functionality. The NRF 232 may be specific to the Public LandMobility Network (PLMN) or network operator, with which it isassociated. The service discovery functionality can allow networkfunctions and UEs connected to the network to determine where and how toaccess existing network functions, and may present the service basedinterface Nnrf.

PCF 222 communicates with other network functions over a service basedNpcf interface, and can be used to provide policy and rules to othernetwork functions, including those within the control plane. Enforcementand application of the policies and rules is not necessarily theresponsibility of the PCF 222, and is instead typically theresponsibility of the functions to which the PCF 222 transmits thepolicy. In one such example the PCF 222 may transmit policy associatedwith session management to the SMF 220. This may be used to allow for aunified policy framework with which network behavior can be governed.

A Unified Data Management Function (UDM) 216 can present a service basedNudm interface to communicate with other network functions, and canprovide data storage facilities to other network functions. Unified datastorage can allow for a consolidated view of network information thatcan be used to ensure that the most relevant information can be madeavailable to different network functions from a single resource. Thiscan make implementation of other network functions easier, as they donot need to determine where a particular type of data is stored in thenetwork. The UDM 216 may employ an interface, such as Nudr to connect toa User Data Repository (UDR) 234. The PCF 222 may be associated with theUDM 216 because it may be involved with requesting and providingsubscription policy information to the UDR 234, but it should beunderstood that typically the PCF 222 and the UDM 216 are independentfunctions.

The PCF 222 may have a direct interface to the UDR 234 or can use Nudrinterface to connect with UDR 234. The UDM 216 can receive requests toretrieve content stored in the UDR 234, or requests to store content inthe UDR 234. The UDM 216 is typically responsible for functionality suchas the processing of credentials, location management and subscriptionmanagement. The UDR 234 may also support any or all of AuthenticationCredential Processing, User Identification handling, AccessAuthorization, Registration/Mobility management, subscriptionmanagement, and Short Message Service (SMS) management. The UDR 234 istypically responsible for storing data provided by the UDM 216. Thestored data is typically associated with policy profile information(which may be provided by PCF 222) that governs the access rights to thestored data. In some embodiments, the UDR 234 may store policy data, aswell as user subscription data which may include any or all ofsubscription identifiers, security credentials, access and mobilityrelated subscription data and session related data.

The Application Function (AF) 224 represents the non-data plane (alsoreferred to as the non-user plane) functionality of an applicationdeployed within a network operator domain and within a 3GPP compliantnetwork. The AF 224 interacts with other core network functions througha service based Naf interface, and may access network capabilityexposure information, as well as provide application information for usein decisions such as traffic routing. The AF 224 can also interact withfunctions such as the PCF 222 to provide application specific input intopolicy and policy enforcement decisions. It should be understood that inmany situations the AF 224 does not provide network services to otherNFs, and instead is often viewed as a consumer or user of servicesprovided by other NFs. An application outside the 3GPP network, canperform many of the same functions as AF 224 through the use of NEF 230.

The UE 202 communicates with network functions that are in the UserPlane (UP) 236, and the Control Plane (CP) 238. The UPF 212 is a part ofthe CN UP 236 (DN 208 being outside the 5GCN). (R)AN node 228 may beconsidered as a part of a User Plane, but because it is not strictly apart of the CN, it is not considered to be a part of the CN UP 236 orUPF 212. AMF 218, SMF 220, AUSF 214, NEF 230, NRF 232, PCF 222, and UDM216 are functions that reside within the CN CP 238, and are oftenreferred to as Control Plane Functions. AF 224 may communicate withother functions within CN CP 238 (either directly or indirectly throughthe NEF 230), but is typically not considered to be a part of the CN CP238.

Those skilled in the art will appreciate that there may be a pluralityof UPFs connected in series between the (R)AN node 228 and the DN 208,and multiple data sessions to different DNs can be accommodated throughthe use of multiple UPFs in parallel.

FIG. 3 illustrates, in a message flow diagram, an example of methods(300) of attaching (305) and re-attaching (375) a UE 202 to a datanetwork 208. The method of attaching (305) comprises the UE 204 sendingan initial attach request to the AN 204 (310) including UE capabilityand, optionally, the requested service and network slice selectionassistance information (NSSAI). The AN 204 forwards the attach requestto the AMF 218. The AMF 218 determines which slice(s) the UE 204 hasselected by accessing a subscriber repository and then authenticates theUE 204 (320) to check whether the UE 204 is permitted to access thenetwork. The AMF 218 then checks the UE mobility policy (330) to verifywhether the UE can access the network in this location. The AMF 218selects the appropriate network slice function SMF 220 based on theinformation received from the UE 204 in the attach request and profileinformation in a subscriber repository. The AMF 218 further interactswith the AUSF 214 to perform the authentication/slice authorizationprocedure by checking the UE identity with the subscriber repository.The procedure determines whether the UE 204 is authorized to access thisslice. Optionally, a setup of the UP connections (360) for a default orUE specific type slice may be performed. The AMF 218 then may send anattach response to the UE 202 via the AN 204. The attach responseincludes a session management—network slice selection assistanceinformation (SM-NSSAI), a temporary UE identifier (Temp UE ID), and MMparameters. When the UE 204 receives the SM-NSSAI, a temp UE ID andmobility management (MM) parameters, the UE 204 may use the informationto assist the network slice selection (e.g., when the UE detaches fromthe network and then re-attaches to the network again).

The method of re-attaching (375) comprises the UE 202 sending an attachrequest (380) to the AN 204. The attach request includes the SM-NSSAI,the Temp UE ID and the MM parameters. The AN 204 forwards the attachrequest to the AMF 218. The slice-specific authorization step (350) andoptionally, the setup of UP connections step (360) described above maybe performed. The AMF 218 then may send an attach response (390) to theUE 202 via the AN 204. The attach response includes the (possiblyupdated) SM-NSSAI, Temp UE ID and MM parameters. Once the UE 202 isattached (or re-attached) to the data network 208, the UE may initiate apacket data unit (PDU) session with the data network 208.

Session management states describe the UP connectivity for a PDU sessionbetween the UE 202 and the SMF 220. For an established PDU session,there may be at least two session management states for a PDU session:an active state (e.g., Session-ACTIVE) and an idle state (e.g.,Session-IDLE). In this description, “Session-ACTIVE” may be used todenote an active state and “Session-IDLE” is used to denote an idlestate. Since the PDU session state is related to data transmissionactivities (UL and DL) of the user, the session state may alternativelybe called a session connection state.

A session management state may be designed for each PDU sessionrespectively. The session management state may be maintained in the UE202 and the SMF 220. The AN 204 and the UP functions may not be aware ofthe session management state. However, the AN 204 and the UP functionsmay maintain the session context of the established PDU session.

When a UE 202 is roaming (in a home routed roaming model), the PDUsession may be served by two SMFs 220 in a chain: one for the visitedpublic land mobile network (VPLMN) and one for the home public landmobile network (HPLMN). The session management state may be updated inthe SMF 220 in the VPLMN, while the SMF 220 in the HPLMN may considerthe PDU session as Session-ACTIVE.

When a UE's PDU session does not have UL or DL activity for a certainperiod, this session's state may be changed to Session-IDLE. The UE mayresume the PDU session(s) after a certain period of time by sending anaccess stratum (AS) message to the AN 204 to activate the data radiobearer (DRB). Alternatively, the UE may resume the PDU session(s) aftera certain period of time by sending an non-access stratum (NAS) messageto the SMF to notify the session activation request. For example, a useris browsing a website. The user may not have any data transmission whileviewing downloaded pages or downloaded video. The UE may again downloadnew data for the same session after reading or viewing the downloadedcontent. In this example, if a time period expires while the user isviewing the downloaded content, the PDU session may be changed toSession-IDLE. When the user begins downloading further data, the PDUsession is then changed to Session-ACTIVE.

In a combined attach and PDU session request procedure, a UE may send arequest for a new session in an attach request message. However, if theUE does not have UL or DL packet transmission after a period of time,the session state may be changed from Session-ACTIVE to Session-IDLE.Thus, by allowing a session to have an active state and an idle state, aUE may set up and keep a new session for “future use” (or near futureuse) even if the UE does not have UL or DL packet transmission for aperiod of time after setting up the new session. Without theSession-IDLE state, the session may have been released prematurely.

The session state attribute may allow the CN 206 to efficiently handlePDU sessions of various applications. The UE 202 may trigger a sessionconnection state transition in the CN 206 by sending an AS message tothe AN 204 to change the state of a DRB (between an active or suspendedstate); the AN 204 may then inform the SMF 220 of the UE request toactivate or deactivate a PDU session in the CN 206. Alternatively, TheUE 202 may trigger a session connection state transition in the CN 206by sending a NAS message to the CN 206; then the CN activates sessionmanagement procedures in the CN and inform the AN 204 to assign radioresources for the PDU session. The session connection state attributemay also allow fast reconnection in the CN 206 when a session isresumed, may reduce signaling overhead in the CP when a session or aradio resource control (RRC) is resumed, may utilize resource usage ofnetwork functions when PDU sessions are idle for long period, and mayavoid RRC signaling regarding session state changes in the CN 206. Inone embodiment, the UE 202 is unaware of the state of sessions in the CN206. In another embodiment, the UE 202 is aware of the sessionconnection state.

FIG. 4 illustrates, in a state model diagram, an example of aSession-IDLE state model 400. The Session-IDLE state model 400 shows howa Session-IDLE state may be represented in the CP (as a session state)and the UP (as a session context) for the UE 202, the AN 204, the SF 220and the UPF 212. When a PDU session is in the Session-IDLE state, theremay be no UP connection dedicated to the PDU session existing between UE202 and the UPF 212 function terminating NG3. The UE 202 may maintainthe session context without activated RAN resources corresponding to thePDU session. In this example, the AN does not maintain any radioresource context corresponding to the PDU session. If the PDU session isserved by only one UPF 212, (i.e., if only the UPF A is present for theUPF 212 in FIG. 4), then the session context may be maintained in theUPF A without AN 204 related information of the NG3. If the PDU sessionis served by two UPFs 212 in a chain (i.e., if only the UPF A and UPF Bwere present for the UPF 212 in FIG. 4), then the session context may bemaintained in both UPF A and UPF B. The UPF terminating NG3 may notmaintain AN 204 related information. Both UPF A and UPF B may maintainthe NG9 tunnel related information. If the PDU session is a multi-homingPDU session (i.e., UPF A, UPF B and UPF C are present as shown in FIG.4), then the session context in the branch point UPF (i.e., UPF A) doesnot maintain AN 204 related information. In this multi-homing PDUsession, the branch point UPF A may maintain the NG9 tunnel relatedinformation towards both UPF B and UPF C. UPF B and UPF C may maintainthe NG9 tunnel related information towards the branch point UPF A.

The UE 202 and the SMF 220 may be in the Session-IDLE state when thedata connection (i.e., NG3) dedicated to the give PDU session is notestablished between the UE 202 and the UPF 212. A NAS message (e.g., aService Request) including the given PDU session identifier (ID) mayinitiate a transition from Session-IDLE to Session-ACTIVE. When a PDUsession is in the Session-IDLE state, the session context in the UE 202and the SMF 220 may be unsynchronized (i.e., the UE 202 and the networkmay have different sets of activated QoS flows (e.g., for guaranteed bitrate (GBR) QoS flows)). During transition from the Session-IDLE state tothe Session-ACTIVE state, the UE 202 may include QoS flows status whichindicate each QoS flow status (i.e., activated or deactivated) of thePDU session in the NAS message (e.g., Service Request), the set ofactivated QoS flows is synchronized between the UE 202 and SMF 220.

FIG. 5 illustrates, in a component diagram, an example of aSession-ACTIVE state model 500. The Session-ACTIVE state model 500 showshow a Session-ACTIVE state may be represented in the CP (as a sessionstate) and the UP (as a session context) for the UE 202, the AN 204, theSF 220 and the UPF 212. A PDU session may be in the Session-ACTIVE statewhen the data connection (i.e., NG3) dedicated to the give PDU sessionis established between the UE 202 and the UPF 214. In the Session-ACTIVEstate, the UL/DL data belonging to the PDU session may be directly sentbetween the UE 202 and the network. The UE 202 may maintain a sessioncontext with activated RAN resources corresponding to the PDU session.The AN 204 may maintain a session context and reserve RAN resource (forGBR QoS flow, if present) corresponding to the PDU session. In the PDUsession is served by only one UPF (i.e., only UPF A), the sessioncontext may be maintained in the UPF A with AN 204 related informationof NG3. If the PDU session is served by two UPFs in a chain (i.e., onlyUPF A and UPF B), the session context may be maintained in the both UPFA and UPF B. The UPF terminating NG3 may maintain AN 204 relatedinformation of NG3. Both UPF A and UPF B may maintain the NG9 tunnelrelated information. If the PDU session is a multi-homing PDU session(i.e., UPF A, UPF B and UPF C), the session context in the branch pointUPF (i.e., UPF A) may maintain AN 204 related information. Branch pointUPF A may maintain the NG9 tunnel related information towards both UPF Aand UPF B. UPF A and UPF B may maintain the NG9 tunnel relatedinformation towards the branch point UPF A.

The AN 204 may be configured with a Session Inactive Timer by the SMF220 when a PDU session is established or activated. If, for the durationof the Session Inactive Timer, there is no UL/DL data detected on thePDU session at the AN 204, then the AN 204 may initiate a sessionconnection state transition procedure. The session connection state inboth the UE 202 and the SMF 220 may enter Session-IDLE for the given PDUsession.

The AN 202 and the SMF 220 may also initiate the PDU sessiondeactivation procedure due to certain causes. For example, an O&Mintervention, an unspecified failure, etc. When a PDU session is in theSession-ACTIVE state, during handover procedures, the AN 204 may sendthe AMF 218 the PDU session ID in a “Handover Required” message.According to the PDU session ID, the AMF 218 may notify thecorresponding SMF 220 to execute the handover procedure.

The following session management (SM) parameters are used in thisdisclosure: “Session-State”, “Activate-Session-when-RRC-Resumed”,“Session-Activity-Timeout”, “SM-Action-for-Idle” and“Keep-UE-Context-For-All”.

The parameter, Session-State, may be used in a UE's PDU session contextof AN 204, SMF 220, UPF 212, UDM 216 and PCF 222. The parameter,Session-State, may have two values: “Session-ACTIVE” and “Session-IDLE”.

The parameter, Activate-Session-when-RRC-Resumed, may be used toindicate whether a PDU session is in the Session-ACTIVE state when anRRC is resumed. This parameter may have two values: “Yes” and “No”. Theparameter may be configured by the PCF 222. The PCF 222 may send thisparameter to the SMF 220. Then the SMF 220 may send this parameter tothe AN 204 and/or to the UE 202 during a session establishmentprocedure.

The parameter, Session-Activity-Timeout, may be a timer parameter in theAN 204, configured by the PCF 222 for individual PDU sessions. Theparameter may be used to monitor activities in the UL and DL of a PDUsession. If the UE 202 does not have UL or DL packets longer than theSession-Activity-Timeout parameter, then the AN 204 may inform the SMF220. The SMF 220 may then either release this PDU session or change thestate of a session from Session-ACTIVE to Session-IDLE, depending on thesession management (SM) policy configured by PCF 222.

The parameter, SM-Action-for-Idle-Session, is a SM policy parameterconfigured by the PCF 222. The PCF 222 may send this parameter to theSMF 220 during a session establishment procedure. TheSM-Action-for-Idle-Session parameter may have two values:“Keep-Idle-Session” and “Release-Idle-Session”. If the value is set to“Keep-Idle-Session”, then the SMF 220 may change the state of the PDUsession from Session-ACTIVE to Session-IDLE. If the value is set to“Release-Idle-Session”, then the SMF 220 may release the idle PDUsession.

The parameter, Keep-UE-Context-For-Idle-Sessions, may be in the UEcontext of the SMF 220 and the UPF 222, as configured by PCF 222. Thisparameter may be used to indicate whether the UE 202 context may be keptin the SMF 220 and UPF 222 when all PDU sessions of the same UE 202 thatare served by the SMF 220 and by the UPF 222 are in the Session-IDLEstate. The Keep-UE-Context-For-Idle-Sessions parameter may have twovalues: “Keep” and “Can-Be-Released”. If theKeep-UE-Context-For-Idle-Sessions parameter is set to “Keep”, then theSMF 220 and the UPF 222 may keep the UE context regardless of thesession state. If the Keep-UE-Context-For-Idle-Sessions parameter is setto “Can-Be-Released”, then at least one of the following may apply:

-   -   The UPF 212 and SMF 220 may keep a complete UE context if their        UE context have at least one active session. However, some        information in the UE context may be released, such as NG3        connection information, including the NG3 tunnel endpoint        identifier and IP address of AN 204.    -   The UPF 212 and the SMF 220 may or may not keep UE context if        all sessions they serve are in the idle state.    -   When a UPF 212 releases the UE context of a UE 202 having all        idle sessions, the UPF 212 may transfer its complete UE context        to the SMF 220. Additionally, the UPF 220 may transfer to the        PCF 222 the charging information of the UE context.

FIG. 6A illustrates, in a state diagram, an example of a sessionmanagement state model 600A in a UE 202. The session management statemodel 600A shows a Session-IDLE state 610 and a Session-ACTIVE state620. An active session (i.e., a session that is in the Session-ACTIVEstate 620) may be transitioned to the Session-IDLE state 610 after arequest by the UE 202 or a request by the AN 204. Such requests mayinclude a RRC connection reconfiguration to deactivate RAN resources forthe PDU session, and a RRC connection release. An idle session (i.e., asession that is in the Session-IDLE state 610) may be transitioned tothe Session-ACTIVE state 620 after a request by the UE 202 (mobileoriginated (MO) data) or a request by the UPF 212 (mobile terminated(MT) data). Such requests may include a RRC connection reconfigurationto activate RAN resources for the PDU session.

FIG. 6B illustrates, in a state diagram, an example of a sessionmanagement state model 600B in a SMF 220. The session management statetransition model 600B shows the Session-IDLE state 610 and aSession-ACTIVE state 620. An active session (i.e., a session that is inthe Session-ACTIVE state 610) may be transitioned to the Session-IDLEstate 620 after a request by the UE 202 or a request by the AN 204. Suchrequests may include a session de-activation request for the PDUsession. An idle session (i.e., a session that is in the Session-IDLEstate 620) may be transitioned to the Session-ACTIVE state 610 after arequest by the UE 202 (MO data) or a request by the UPF 212 (MT data).Such requests may include a RRC connection reconfiguration to activateRAN resources for the PDU session.

FIG. 6C illustrates, in a component diagram, an example of a sessionmanagement state model 600C for multiple PDU sessions. A UE 202 may havemultiple established PDU sessions using multiple SMFs 220 and UPFs 212.The NextGen system supports the independent session connection state perPDU session (e.g., Session A is in Session-IDLE state, while Session Band Session C are in Session-ACTIVE state. Session A and Session B areserved by SMF A, while Session C is served by SMF B). When multiple PDUsessions are activated for a UE 202, the AN 204 may be configured withindividual Session Inactive Timers by the SMF(s) 220 for each PDUsession during the session activation procedure. When the UE 202 is inthe CN-IDLE state, the session connection state of each PDU session maybe Session-IDLE. When the UE 202 requests to enter the CN-CONNECTEDstate from the CN-IDLE state (e.g., a Service Request), the UE 202 mayalso indicate the PDU session(s) to be activated. The session connectionstatus for the requested PDU session(s) may be changed to Session-ACTIVEin the UE 202 and SMF 220, while the other PDU sessions(s) (if any) mayremain in Session-IDLE. Whether or not the UE 202 has an activated PDUsession, the NextGen system may support the activation of additional PDUsessions.

When a session is in a Session-IDLE state 610, a RRC can be in any state(e.g., RRC-CONNECTED, RRC-IDLE, RRC-INACTIVE). If all PDU sessions arein the Session-IDLE state, then the RRC may be in any states, themobility state is MM-Registered, and the CN state is either CN-IDLE orCN-CONNECTED. The DRB may be suspended. Thus there is no AS signalingfor idle sessions. The UE 202, the AN 204, the UPF 212, the SMF 220, theUDM 216 and the PCF (222) may store a relevant UE context, includingtunnel information, for a fast connection resumption. However, the NG3tunnel information may not be updated in the case of UE mobility or UPF212 relocation. Tunnel maintenance procedures may not be performed.Furthermore, an NG3 tunnel of idle sessions may be removed from routingtables of the AN 204 and the UPF 212. The tunnel information will beupdated when a session changes its state from Session-IDLE toSession-ACTIVE. In a UE context of the AN 204, the UPF 212, the SMF 220,the UDM 216 and the PCF 222, the parameter Session-State may be marked“Session-IDLE”. NAS signaling is not required for idle sessions. In theUPF 212, for idle sessions, the TFTs may not be available in the packetclassification function of UPF 212. Resources used for session data rate(AMBR/MBR/GBR) monitoring and charging may be released.

When a session is in a Session-ACTIVE state 620, and a RRC is in aRRC-CONNECTED state, the DRB/AS/NAS signaling are established. Themobility state is MM-Registered and the CN state is CN-CONNECTED.Network functions serving PDU sessions, including the UE 202, the AN204, the UPF 212, the AMF 218, the SMF 220, the UDM 216 and the PCF 222,have relevant UE context information. In the UE contexts of the AN 204,the UPF 212, the SMF 220, the UDM 216 and the PCF 222, the parameterSession-State is marked “Session-ACTIVE”. In the UPF 212, the trafficflow template (TFT) is available at the packet classification functionof UPF 212. The TFT is used to classify packets into quality of service(QoS) flows. Therefore, the more TFTs that are in use, the higher thesearch complexity at the UPF 212. Thus, only the TFTs of active sessionsare searched for ingress packets in UPF 212. In the AN 204 and the UPF212, resources for the PDU session data rate (aggregate maximum bit rate(AMBR)/maximum bit rate (MBR)/guaranteed bit rate (GBR)) monitoring andcharging are in operation.

The SMF 220 may change the state of a PDU session from Session-ACTIVE toSession-IDLE based on UE 202 and AN 204 requests, or based on its owndecision. The UE 202 and UPF 212 may inform the SMF 220 about thepresence of UE data so that the SMF 220 can change the state of asession from Session-IDLE to Session-ACTIVE. It is possible to changethe state of individual sessions or a group of sessions. The SMF 220informs the UPF 212 so that the UPF 212 either must keep or canoptionally remove the UE context, depending on the SM policy for thisPDU session configured by the PCF 222.

When the RRC of the UE 202 is in a RRC-CONNECTED state and the AN 204changes the RRC to RRC-IDLE or RRC-INACTIVE CONNECTED mode, the state ofall the UE's 202 PDU sessions may be set to the Session-IDLE state.

When a RRC connection is resumed, the CN state is changed from CN-IDLEto CN-CONNECTED. For MO transmission, the UE 202 may send an AS requestto the AN 204 to resume the RRC connection. This request may include theDRB identifiers (IDs) to be resumed. Alternatively, the UE 202 may senda NAS request to the SMF 220 to indicate which session is to be resumed.It is possible to resume SM for some specific PDU sessions. For MTtransmission, the UPF 212 may send a UE context update request to theSMF 220. The SMF 220 interacts with the AMF 218 to page the UE 202 inorder to activate the RRC connection.

To support individual session (de-)activation, the UE 202 and the AN 204may initiate a procedure to suspend or resume DRBs. If a DRB issuspended, the session state in the CN 206 may be changed toSession-IDLE. If a DRB is resumed, the session state in the CN 206 maybe changed to Session-ACTIVE.

Session management procedures for session establishment, sessionrelease, session modification, RRC state transition, and session statetransition are described below.

FIG. 7 illustrates, in a message flow diagram, an example of a sessionestablishment procedure (700), in accordance with an embodiment of thepresent invention. Steps to the session establishment procedure (700)may be performed by several components of the non-roaming architecture210 to establish a session between the UE 202 and the DN 208. The PCF222 may have a SM policy that includes information regarding networkslice-specific preferable logical UL and DL paths between the AN 204 andthe UPF 212.

The method (700) comprises the UE sending a new NAS session requestmessage (705) that includes a SM-NSSAI, a UE temp ID, and a UE-generatedsession ID, service type, and a domain name network (DNN) to the AMF 218via the AN204. It is noted that when the PDU session is created togetherwith a UE initial attach or re-attach procedure for some specificnetwork slices, the UE may provide the UE-generated session ID togetherwith the initial attach or re-attach request. The AMF 218 uses theSM-NSSAI to select a SMF 220 and forward the session request message tothe selected SMF 220 (710), together with an IP address of the servingAN. The AMF 218 may store the ID of the selected SMF 220. When the SMF220 receives the request from the AMF 218, the SMF 220 may store the IDof the AMF 218 that serves the UE 202. The SMF 220 may access usersubscription information in the UDM 216 for service authorization (715)(i.e., SMF-UDM service authorization messaging). If the service is notauthorized, then the SMF 220 may send an appropriate session creationresponse message (760) is sent to the UE 202 via the AMF 218. Thesession creation response may include a session denial code.

If the service is authorized (715), then the setup of the UP connections(360) for a default or UE specific type slice may be performed. Thesetup of the UP connections (360) may include the SMF 220 obtaining UEpolices from the PCF 222 (720), including the SM, the QoS, and thecharging policies (i.e., SMF-PCF UE policies retrieval (SM, QoS,charging) messaging). The SMF 220 may also allocate the IP address(es)for the UE 202 if the PDU session is an IP-based session. The SM policymay include at least the following information: the preferred UPF(s) 212to support mobile edge computing (MEC) applications; the parameterSession-Activity-Timeout; the parameterKeep-UE-Context-For-Idle-Sessions; the parameterSM-Action-for-Idle-Session; and the parameterActivate-Session-when-RRC-Resumed.

Optionally, the SMF 220 may subscribe to the AMF 218 for UE mobilityinformation (725), if mobility-pattern based session managementoptimization is to be performed and if the SMF has not yet subscribed tothe AMF 218 for the information. It is noted that the SMF-AMF UEmobility information subscription messaging (725) may be an independentprocedure that may take place anytime before, after or during sessionestablishment. In this example, the SMF-AMF UE mobility informationsubscription is shown within the session establishment procedure.

Next, the SMF 220 may send to the serving AN 204, via the AMF 218, an ANresource setup request message (730). The request may include the UEtemp ID, the session ID, the QoS profile, and the selected IP address ofthe UPF 212. The request may also include the Session-Activity-Timeoutparameter and the Activate-Session-when-RRC-Resumed parameter.

Optionally, if the UE 202 provided session ID is included in the attachrequest, the AN 204 may perform admission control for the requested PDUsession according to the QoS profile. If the PDU session is accepted,the AN 204 may establish (i.e., set up) a DRB (735) according to the QoSprofile. It is noted that for some services, although UE may not requestfor a new session during attach procedure, the CN 206 may stillestablish the UP path, even though there is no DRB is establishedbetween UE 202 and the AN204.

The AN 204 may then send to the SMF 220, via the AMF 218, an AN resourcesetup response message (740). The AN 204 may store all UE-relatedinformation in a UE-specific context profile, include the Session-Stateparameter. Next, the SMF 220 may select the UPF 212 based on thepreferred UPF(s) policy, if available, and the current traffic load ofthe UPFs 212. The SMF 220 may send a UPF session setup request message(745) to the selected UPF 212, which may include at least the UE tempID, the session ID, the IP address(es) of the UE 202, the QoS andcharging policies, the DNN, and the Keep-UE-Context-For-Idle-Sessionsparameter. The UPF 212 may store all UE-related information in aUE-specific context, which may include the UE temp ID, the session ID,the AN 204, the IP address(es) of UE 202, the QoS and charging policies,and other information. It is noted that the session ID may be omittedfor some UE types, such as simple Internet of things (IoT) devices,which access only one slice and only one PDU session per network slice.

Next, the UPF 212 may send a UPF session setup response message (750) tothe SMF 220. The SMF 220 may store all UE-related information in a SM UEcontext profile, including the Session-State parameter. The SMF 220 maythen send a session creation response message (755) to the AMF 218,which may include the UE temp ID and the session ID. The AMF 218 maytrigger mobility management procedures. The SMF 220 may then send a NASsession creation response message (760) to the UE 202 via the AMF 218.If the session request is accepted, the session creation response mayinclude the session ID, the assigned IP address(es), an optional QoSprofile, and the service and session continuity (SSC) mode. The SM maystore UE context information, including SM policy, QoS and chargingpolicies, the assigned IP address(es), the AMF ID, the AN ID, the UPFID, the NG3 tunnel information, and other parameters. The two steps 755and 760 may be combined. For example, the SMF 220 may send one messagecontaining two parts: one for the AMF 218 and one for the UE 202. Afterreceiving the combined session creation response message, the AMF 218may detach the information for itself and forward the UE's part to theUE 202. As noted above, if the session request is reject, the sessioncreation response may include an error code. This error code may be“Un-authorized Service Request”, “Network Resources Outage”, “Not EnoughCredit for Charging”, or another error code. It is noted that if the UE202 requests a new session in an initial attach and re-attach request,step (760) may be omitted. In this case, in the initial attach andre-attach procedures, the AMF 218 may send an attach response messagethat includes session management information. The SM information mayinclude the session ID and the QoS profile.

Optionally, the SMF 220 may send UE session management information(i.e., via a SMF-UE context update (765) procedure) to the UDM 216. Alsooptionally, the AMF 218 may send UE mobility management relatedinformation (i.e., via an AMF-UDM UE context update (770) procedure) tothe UDM 216. Optionally, the SMF 220 and the PCF 222 may perform aSMF-PCF session update procedure (775) where the actual parameters ofthe PDU session may be sent from the SMF 220 to the PCF 222. It is notedthat the AN 204 and the UPF 212 may setup a tunnel if this tunnel doesnot yet exist.

FIG. 8 illustrates, in a message flow diagram, an example of the SMF-AMFUE mobility information subscription procedure (725), in accordance withan embodiment of the session establishment procedure (700). The SMF 220may send to the AMF 218 (or the AMF 218 may receive from the SMF 220) aSMF-AMF UE mobility information request (826) message. The message (826)may include one or more identifiers to identify the UE 202 (such as tempUE ID, international mobile subscriber identity (IMSI), GUTI), themobility time window, and the type of subscription. The mobility timewindow indicates the time span of the requested UE mobility information.The type of subscription indicates whether the subscription is aone-time information retrieval or may use periodic information updates.The SMF 220 then may receive from the AMF 218 (or the AMF 218 may sendto the SMF 220) a SMF-AMF UE mobility information update (828) message.The message may include the identifiers of the set of ANs 204 that maypotentially serve the UE in the specified mobility time window. The AMF218 may perform the mobility information update (828) upon receiving therequest (826), and, if the request (826) indicates a periodic update,when the requested mobility information changes. The AMF 218 maydetermine the service AN 204 set according to the mobility pattern ofthe UE 202. Other steps may be added to the procedure (725).

FIG. 9 illustrates, in a message flow diagram, an example of the SMF-UDMUE context update procedure (765), in accordance with an embodiment ofthe session establishment procedure (700). The SMF 220 may send to theUDM 216 (or the UDM 216 may receive from the SMF 220) a SMF-UDM UEcontext update request (966) message. The message (966) may includeidentifiers to identify the UE 202 (such as temp ID, IMSI, GUTI), andthe UE context or new values of parameters of the UE context that havechanged. The SMF 220 may then receive from the UDM 216 (or the UDM 216may send to the SMF 220) a SFM-UDM context update response (968) messageto confirm that the UE context has been updated in the UDM 216. Othersteps may be added to the procedure (765).

FIG. 10 illustrates, in a message flow diagram, an example of a AMF-UDMUE context update procedure (770), in accordance with an embodiment ofthe session establishment procedure (700). The AMF 218 may send to theUDM 216 (or the UDM 216 may receive from the AMF 218) a AMF-UDM UEcontext update request (1072) message to update the mobility managementparameters for a UE 202. The message (1072) may include identifiers toidentify the UE 202 (such as temp UE ID, IMSI, GUTI) and the UE contextor new values of parameters of the UE context that have changed. The AMF218 may then receive from the UDM 216 (or the UDM 216 may send to theAMF 218) an AMF-UDM UE context update response (1074) message to confirmthat the mobility management parameters of in the UE context have beenupdated in the UDM 216. Other steps may be added to the procedure (770).

FIG. 11 illustrates, in a message flow diagram, an example of a SMF-PCFsession update procedure (775), in accordance with an embodiment of thesession establishment procedure (700). The SMF 220 may send to the PCF222 (or the PCF 222 may receive from the SMF 220) a SMF-PCF UE sessionupdate request (1176) message to update the session parameters for a UE202. The message (1176) may include identifiers to identify the UE 202(such as temp UE ID, IMSI, GUTI) and the UE context (session management,QoS parameters, charging information) or new values of parameters of theUE context that have changed. The SMF 220 may then receive from the PCF222 (or the PCF 222 may send to the SMF 220) a SMF-PCF session updateresponse (1178) message to confirm that the session managementparameters of the UE 202 have been updated in the PCF 136. Other stepsmay be added to the procedure (775).

FIG. 12 illustrates, in a flowchart, an example of a method ofestablishing a session (1200), in accordance with the sessionestablishment procedure (700). The method (1200) is performed by the SMF220. The SMF 220 may be implemented as a session management functionmodule on a server on the CN 206. The SMF 220 may be configured toreceive a session request message (1210). The session request messagemay be from an AMF 218 that received the session request message from aUE 202. Once the SMF 220 receives the session request message, the SMF220 may determine if the UE 202 is authorized to request the service(1220). To perform this service authorization, the SMF 220 may accessuser subscription information in the UDM 216. If the service is notauthorized (1220), then the SMF 220 may send an appropriate sessioncreation response message (760) to the UE 202 via the AMF 218. Asdescribe above, the session creation response may include a sessiondenial code. If the service is authorized (1220), and if amobility-pattern based session management optimization is to beperformed, and if the SMF 220 has not yet subscribed to the AMF for theinformation, (1230) then the SMF 220 may subscribe to the AMF 218 for UEmobility information (725), as described above. It is noted that, asdescribed above, steps (1230) and (725) may be performed at any timebefore, during or after the method (2040).

The SMF 220 may obtain UE policies from the PCF 222 (720), as describedabove. Next, the SMF 220 may send to the serving AN 204 via the AMF 218the resource setup request message (730), as described above. The SMF220 may then receive the resource setup response message from the AN 204via the AMF 218 (740), as described above. Next, the SMF 220 may send aUP setup request message to a selected UPF 212 (745), as describedabove. Next, the SMF 220 may receive a session setup response messagefrom the UPF 212 (750), as described above. The SMF 220 may then send asession creation response message (755) to the AMF 218, as describedabove. The SMF 220 may then send a session creation response message(760) to the UE 202 via the AMF 218, as described above.

Other steps may be added to the method (2040), including the SMF 220storing all UE-related information in a SM UE context profile, includingthe Session-State parameter. The SMF 220 may also optionally send UEsession management information to the UDM 216 (765).

FIG. 13 illustrates, in a message flow diagram, an example of a sessionmodification procedure (2060), in accordance with an embodiment of thepresent invention. A PDU session modification procedure may be triggeredby the PCF 222, the UE 202, and the SMF 220. A first possible triggerfor session modification occurs when the PCF 222 sends to the SMF 220 aPCF-SMF session modification request (1310 a). The request may includethe temp UE ID, the session ID, and new SMIQoS/charging policyparameters. A second possible trigger for session modification occurswhen the UE 202 sends to the SMF 220, via AMF 218, a UE-SMF sessionmodification request for an active session (1310 b). The request mayinclude the SM-NSSAI, the temp UE ID, the session ID, a list ofparameters to be changed and their new values, and a UE time zone. Athird possible trigger for session modification occurs when the SMF 220creates a SMF session modification request (1310 c) based on current UEpolicies, and other factors (e.g., load changes in the UPF 212 and theAN 204).

If the first and second possible triggers were responsible for thesession modification request, then the SMF 220 may verify the sessionmodification requests (1320). If the request comes from the PCF 222 forUE policy updates (1310 a), then the new policy update may be stored ina local memory of the SMF 220. The SMF 220 may create a sessionmodification request to the AN 204 and the UPF 212 based on the newpolicy parameters. If the request comes from the UE 202 (e.g., for newQoS parameters (higher MBR or higher GBR)) (1310 b), the SMF 220 mayverify the request with the current UE policies. If the UE request (1310b) is allowed, then the SMF 220 may create a session modificationrequest to the AN 204 and the UPF 212 based on the UE request. If the UErequest (1310 b) is not allowed, then the SMF 220 may send a cause codeto UE (1390 b) and the other steps in the procedure (1300) may bedisregarded.

The UE 202 may request session modification that may be out of policiesstored in the SMF 220. For example, the UE 202 may request an additionalGBR flow for a current PDU session that has no GBR flows. If the UE 202requests additional GBR flow, then the SMF 220 and PCF 222 may perform aUE policy retrieve procedure. The SMF 220 may send to the PCF 222 aSMF-PCF UE policy request message (1330), which may include the requiredpolicy for the additional PDU flow that the UE requested. The PCF 222may return to the SMF 220 a SMF-PCF UE policy response message (1335),which may include the UE policy.

Next, the SMF 220 may send to the AN 204, via the AMF 218, a SMF-ANsession modification request message (1340). The request may include newSM parameters and/or new QoS parameters. Optionally, the AN 204 may thenperform admission control (1350) if a new GBR flow is requested or acurrent GBR flow is modified. If the QoS parameter changes are accepted,the AN 204 may optionally perform a session modification procedure withthe UE 202. The AN 204 may send to the UE 202 a AN-UE sessionmodification request message (1360). The request may include new QoS, SMor policy parameters. After applying new QoS, SM or policy parameters,the UE 202 may send to the AN 204 a AN-UE session modification responsemessage (1365).

Next, the AN 204 may send to the SMF 220, via the AMF 218, a SMF-ANsession modification response message (1370), which may include eitheran acknowledgment or a cause code. If the SMF-AN session modificationresponse message included a cause code, steps (1380) and (1385) may bedisregarded. Otherwise, the SMF 220 and the UPF 212 may perform aSMF-UPF session modification procedure. The SMF 220 may send to the UPF212 a SMF-UPF session modification request message (1380), which mayinclude the temp UE ID, the session ID, and new parameters of the PDUsession. The UPF 212 may receive new session parameters and checkwhether the new parameters can be supported. If the new parameters canbe supported, the UPF 212 may reconfigure its resources to support thePDU session. The UPF 212 may then send to the SMF 220 a SMF-UPF sessionmodification response message (1385), which may include either anacknowledgment or a cause code. Next, the SMF 220 may send a response tothe original request. If the session modification request came from thePCF 222, then the SMF 220 may send to the PCF 222 a PCF-SMF sessionmodification response message (1390 a), which may either include anacknowledgment or a cause code. If the session modification request camefrom the UE 202 (1310 b) or the SMF 220 (1310 c), the SMF 220 may sendto the PCF 222 a PCF-SMF session modification response message (1390 a)which contains new session parameters. If the session modificationrequest came from the UE 202 (1310 b), then the SMF 220 may send to theUE 202 a UE-SMF session modification response message (1390 b), whichmay either include an acknowledgment or a cause code. Optional, the SMF220 may perform a UE context update procedure (765) with the UDM 216.

FIG. 14 illustrates, in a flowchart, an example of a method modifying asession (1400), in accordance with the session modification procedure(1300). The method (1400) is performed by the SMF 220. The SMF 220 maybe configured to determine that a session modification is to beperformed (1410). This determination (1410) may be due to the SMF 220receiving a PCF-SMF session modification request message from the PCF222. Alternatively, this determination (1410) may be due to the SMF 220receiving a UE-SMF session modification request message from the UE 202.Alternatively, this determination (1410) may be due to the SMF 220generating a SFM session modification request message based on currentUE policies and other factors (e.g., load changes in the UPF 212 and theAN 204). If the determination (1410) was made due to requests from thePCF 222 or the UE 202 (1420), then the SFM 220 is configured to verifythe received session modification requests (1320), as described above.The SMF 220 may then send the SMF-AN session modification requestmessage to the AN 204 (1340), via the AMF 218, as described above. Next,the SMF 220 may receive the SMF-AN session modification response messagefrom the AN 204 (1370), via the AMF 218, as described above. Next, theSMF 220 may send to the UPF 212 the SMF-UPF session modification requestmessage (1380), as described above. The SMF 220 may then receive fromthe UPF 212 the SMF-UPF session modification response message (1385), asdescribed above. If the session modification was due to a request fromthe SMF 220 (1430), then the SMF 220 may send to the PCF 222 a PCF-SMFsession modification response message (1390 a), as described above. Ifthe session modification was due to a request from the UE 202 (1440),then the SMF 220 may send to the PCF 222 a PCF-SMF session modificationresponse message (1390 a), and then the SMF 220 may send to the UE 202 aUE-SMF session modification response message (1390 b), as describedabove.

Other steps may be added to the method (2080), including sending aPCF-SMF session modification response message to the PCF 222 if the PCF222 sent the original session modification request to the SMF 220.Alternatively, the SMF 220 may send UE-SMF session modification responsemessage to the UE 202 if the UE 202 sent the original sessionmodification request to the SMF 220. Additionally, the SMF 23 mayoptionally send a SMF-PCF UE policy request message to the UPF 212(1330), and receive a SMF-PCF UE policy response message from the UPF212 (1335), as described above.

FIG. 15 illustrates, in a message flow diagram, an example of a sessionrelease procedure (1500), in accordance with an embodiment of thepresent invention. The PDU session release procedure (1500) may betriggered by the UE 202, the AN 204, the UPF 212 and the SMF 220. Afirst possible trigger for the PDU session release occurs when the UE202 sends to the SMF 220 a UE session release request message (1510 a).The message may include the SM-NSSAI, the temp UE ID and the session ID.A second possible trigger for the PDU session release occurs when the AN204 sends to the SMF 220 an AN session release request message (1510 b).The AN 204 may report one of: a congestion condition for some PDUsessions, no traffic activity for a long period, and/or otherconditions. A third possible trigger for the PDU session release occurswhen the UPF 212 sends to the SMF 220 a UPF session release requestmessage (1510 c). The UPF 212 may report at least one of a congestioncondition for some PDU sessions, a charging policy violation (i.e.,time-based, data volume-based, etc.), and/or other conditions. A fourthpossible trigger for the PDU session release occurs when the SMF 220decides to release a PDU session by its own logic (1510 d), or byreceiving information from the UE 202, the AN 204 and/or the UPF 212.Once a decision is made by the SMF 220 to release a session, there aretwo options for a session release procedure for the UE 202 and the AN204.

In the first session release procedure option, the SMF 220 may send tothe UE 202, via the AMF 218, a SMF-UE session release request message(1520 a), which may include the UE temp ID, the session ID, and a causecode. The value of the cause code may indicate the source of the sessionrelease request, such as: “Session Release by UE” (corresponding to step1510 a); “Session Release by AN” (corresponding to step 1510 b);“Session Release by UPF” (corresponding to step 1510 c); and “SessionRelease by SMF” (corresponding to step 1510 d). Next, the UE 202 mayrelease its DRB resources and PDU session context. The UE 202 may sendto the SMF 220, via the AMF 218, a SMF-UE session release responsemessage (1530 a) to confirm the release of AN 204 resources for thereleased PDU session. Next, the SMF 220 may send to AN 204, via the AMF218, a SMF-AN session release request message (1540), which may includethe UE temp ID and the session ID. Next, the AN 204 may remove the UE'sPDU context, and releases DRB resources. The AN 204 may send to the SMF220, via the AMF 218, a SMF-AN session release response message (1550)to confirm the release of AN 204 resources for the released PDU session.

In the second session release procedure option, the SMF 220 may send tothe AN 204, via the AMF 218, a SMF-AN session release request message(1540), which may include the UE temp ID, the session ID, and a causecode. The value of the cause code may indicate the source of the sessionrelease request, such as: “Session Release by UE” (corresponding to step1510 a); “Session Release by AN” (corresponding to step 1510 b);“Session Release by UPF” (corresponding to step 1510 c); and “SessionRelease by SMF” (corresponding to step 1510 d). Next, the AN 204 maysend to the UE 202 an AN-UE session release request message (1520 b).The message indicates the DRB to be released (which is being used toserve the PDU session) and a cause code. Next the UE 202 may release itsDRB resources and PDU session context. The UE 202 may send to the AN 204an AN-UE session release response message (1530 b). Next, the AN 204 mayremove the UE's PDU context, and release DRB resources. The AN 204 maysend to the SMF 220 a SMF-AN session release response message (1550) toconfirm the release of AN resources for the released PDU session.

Next, the SMF 220 and the UPF(s) 212 may perform a SMF-UPF sessionrelease procedure. The SMF 220 may send to the UPF 212 a SMF-UPF sessionrelease request message (1560 a). The message may include the temp UE IDand the session ID. Next, the UPF 212 may remove the UE's PDU sessioncontext, and release resources that serve the PDU session. The UPF 212may send to the SMF 212 a SMF-UPF session release response message (1560b). It is noted that the UPFs 212 may send charging information to thePCF 222 via the SMF 220. Optional, the SMF 220 and the UDM 216 mayperform a SMF-UDM UE context update procedure (1570), in which the UDM216 may remove the UE's PDU session information. Next, the SMF 220 andthe PCF 222 may perform a SMF-PCF UE context update procedure (1580).The SMF may forward charging information to the PCF 222. The PCF 222 mayremove the PDU session information of the released PDU session.

FIG. 16 illustrates, in a flowchart, an example of a method of releasinga session (1600), in accordance with the session release procedure(1500). The method (1600) is performed by the SMF 220. The SMF 220 maybe configured to determine to release a session (1610), as describedabove with reference to FIG. 15. Once the determination (1610) is made,the SMF 220 may send the SMF-UE release request message (1520 a) to theUE 202, via the AMF 218, as described above. Next, the SMF 220 mayreceive the SMF-UE release response message (1530 a) from the UE 202,via the AMF 218, as described above. Next, the SMF 220 may send theSMF-AN session release request message (1540) to the AN 204, via the AMF218, as described above. Next, the SMF 220 may receive the SMF-ANsession release response message (1550) from the AN, via the AMF 218, asdescribed above. Next, the SMF 220 may send the SMF-UPF session releaserequest message (1560 a) to the UPF 212, as described above. Next, theSMF 220 may receive the SMF-UPF session release response (1560 b) fromthe UPF 212, as described above. Next, the SMF may perform a SMF-PCF UEcontext update procedure (1570) with the PCF 222, as described above.Other steps may be added to the method (1600), including the SMF 220 andthe UDM 216 perform an optional SMF-UDM UE context update procedure(765), as described above.

FIG. 17 illustrates, in a flowchart, another example of a method ofreleasing a session (1700), in accordance with the session releaseprocedure (1500). The method (1700) is performed by the SMF 220. The SMF220 may be configured to determine to release a session (1610). Thedetermination (1610) may be based on receiving a session release requestmessage from the UE 202. Alternatively, the determination (1610) mayalso be based on receiving a session release request message from the AN204. Alternatively, the determination (1610) may also be based onreceiving a session release request message from the UPF 212.Alternatively, the determination (1610) may also be based on logic ofthe SMF 220. Once the determination is made, the SMF 220 may send theSMF-AN session release request message (1540) to the AN 204, via the AMF218, as described above. Next, the SMF 220 may receive the SMF-ANsession release response message (1550) from the AN, via the AMF 218, asdescribed above. It is noted that prior to the SMF receiving the SMF-ANsession release response message (1550) from the AN, the AN would havesent to the UE an AN-UE session release request, and received from theUE an AN-UE session release response, as described above. Next, the SMF220 may send the SMF-UPF session release request message (1560 a) to theUPF 212, as described above. Next, the SMF 220 may receive the SMF-UPFsession release response (1560 b) from the UPF 212, as described above.Next, the SMF may perform a SMF-PCF UE context update procedure (1570)with the PCF 222, as described above. Other steps may be added to themethod (1700), including the SMF 220 and the UDM 216 perform an optionalSMF-UDM UE context update procedure (765), as described above.

FIG. 18 illustrates, in a message flow diagram, an example of a PDUsession connection state transition procedure (1800), in accordance withan embodiment of the present invention. The UE 202 may have its ownlogic to determine whether the session connection state of a session canbe changed. The AN 204 may monitor UL/DL activities of the PDU sessionto request the SMF 220 to change the session connection state toSession-IDLE. The procedure (1800) may be triggered by the UE 202 or bythe AN 204. A first possible trigger for the PDU session connectionstate transition procedure occurs when the UE 202 sends to the SMF 220 asession connection state transition request (1810 a) (eitherSession-ACTIVE or Session-IDLE). The message (1810 a) may include thetemp UE ID, the SM-NSSAI(s), the session ID(s), and the new sessionconnection state. A special value of the session ID (e.g., wildcard) maybe used to represent that all the PDU sessions being served by the sameSM indicated in SM-NSSAI are in the idle state. Another possible triggerfor the PDU session connection state transition procedure occurs whenthe AN 204 monitors PDU session activities of all PDU sessions and theAN 204 detects no UL and DL packets of a session after a SessionInactive Timer set by the SMF 220 during a session establishmentprocedure (700). The AN 204 sends to the SMF 220 a Session-IDLE statetransition request (1810 b), which requests to set the state of a singlePDU session, or multiple PDU sessions, to the Session-IDLE state. Themessage may include the temp UE ID, the SM-NSSAI(s), the session ID(s)and the AN ID. A special value of the session ID (e.g., wildcard) may beused to represent that all the PDU sessions being served by the same SMindicated in SM-NSSAI are in the idle state.

The parameter for the session connection state of the UE context of theSM is set to the new state as requested (1820). Next, the SMF 220 maynotify the AN 204 of the session connection state transition (1830 a).The notification may include the UE ID, the session ID, and otherinformation. If the session connection state is changed to Session-IDLE,then the SMF 220 may request the AN 202 to release PDU sessioninformation, including NG3 tunnel information. The AN 204 may alsorelease radio resources that serve the PDU session. If the sessionconnection state is changed to Session-ACTIVE, then the SMF 220 may sendto the AN the PDU session context, including the NG3 tunnel informationand QoS profile. The AN 204 may then prepare radio resources to servethe PDU session according to the QoS profile. If the QoS flows requireadmission control, the AN 204 may perform the admission control. Next,the AN 204 may send to the SMF 220 a session connection state transitionresponse (1830 b). The response may be an acknowledgement or a error(cause) code. If the response is a cause code, then the remaining stepsin the procedure are not performed.

If the response (1830 b) is not a cause code, then the SMF 220 mayrequest the UPF 212 to perform an “Update UE Context” service (1840).The SMF 220 may request the UPF 212 to release NG3 tunnel informationform the UE context in the UPF 212 if the session connection state ischanged to Session-IDLE. In this request, the tunnel endpoint ID of theAN 204 may be set to NULL. If the session connection state is changed toSession-ACTIVE, the SMF may request the UPF 212 to add the IP address ofthe AN 204 for NG3 tunnel information. Next, the SMF 220 may request theAMF 218 to perform an “Update UE Context” service (1850). The sessionconnection state in the UE context of the AMF 218 may be set to the newsession connection state. The notification may include the UE ID, thesession ID, and new session connection state requested. The AMF 218 maystore the session connection state of the session in its UE context.

Next, the SMF 220 may notify the UE 202 of the new session connectionstate (1860 a). The notification may include the session ID, the newsession connection state, and a cause code if the SMF 220 received acause code from the AN 204. Next, the UE 202 may send a Session-IDLEstate transition response message (1860 b) to the SMF 220. Next, the SMF220 requests the PCF 222 to perform an “Update UE Context” service(1870). The new session connection state may be sent to the PCF 222. Theservice request from the SMF 220 may include the UE ID, the session ID,and the new session connection state. The request (1870) may be theSMF-PCF UE context update procedure (1580), as described above.

FIG. 19 illustrates, in a flowchart, an example of a method ofperforming a state transition (1900), in accordance with the PDU sessionconnection state transition procedure (1800). The method (1900) may beperformed by the SMF 220. The SMF 220 may be configured to receive asession state transition request (1910). The request may be from the UE202 or from the AN 204. Next, the SMF 220 may update the session connectstate parameter of the UE context of the SM to the requested connectionstate (1820). Next, the SMF 220 may send a session connection statetransition request message to the AN 204 (1830 a). Next, the SMF 220 mayreceive a session connection state transition response message from theAN 204 (1830 b). Next, the SMF 220 may send an “Update UE Context”service request to the UPF 212 (1840). Next, the SMF 220 may send an “UEContext Update” service request to the AMF 218 (1850). Next, the SMF 220may send a session connection state transition notification to the UE202 (1860 a). Next, the SMF 220 may receive a session connection statetransition response from the UE 202 (1860 b). Next, the SMF 220 may sendan “Update UE Context” service request to the PCF 222 (1870). Othersteps may be added to the PDU session connection state transitionprocedure (1800).

FIG. 20 illustrates, in a message flow diagram, an example of an RRCsuspend procedure (2000), in accordance with an embodiment of thepresent invention. A result of this procedure (2000) may be thetransitioning of a PDU session from an active state to the PDUSession-IDLE state. The UE 202 may have its own logic to determinewhether the state of RRC can be suspended to save energy, but withoutreleasing the current session(s). In this scenario, the state of thecurrent session(s) may be set to Session-IDLE in the AN 204, the UPF212, the SMF 220, the PCF 222, and optionally in the UDM 216. The UE 202may have multiple PDU sessions, where each session may be served by asingle UPF 212 or multiple UPFs 212. The UE may have access to multiplenetwork slices, where each slice may have a separate SMF 220 to servethe UE 202. The RRC suspend procedure (2100) may be triggered by the UE202 or the AN 204. A first possible trigger for the Session-IDLE statetransition occurs when the UE 202 sends to the AN 204 a UE-AN RRCsuspend request message (2010 a). A second possible trigger for theSession-IDLE state transition occurs when the AN 204 detects noactivities in the UL and the DL (2010 b). After a UE-Activity-Timeouttimer expires, the AN 204 may suspend the RRC connection.

Next, the AN 204 and the AMF 218 may perform an AN-AMF UE CN stateupdate procedure (2020). The AN 204 may send to the AMF 218 an AN-AMF UECN-IDLE state transition request message (2020 a), which may include thetemp UE ID, the new CN-IDLE state of the UE 202, and a cause code “UERequests RRC Suspension” (corresponding to step 2010 a) or “All SessionsIdle” or “No Data Activities” (corresponding to step 2010 b). The AMF218 may then change the state of the UE 202 to CN-IDLE and stop the AMF218 procedures with the UE 202. The AN may then send to the UE 202 aAN-AMF UE CN-IDLE state transition response message (2020 b).

Next, the AN 204 and the UE 202 may perform a UE-AN RRC suspendprocedure (2030). The AN 204 may send to the UE 202 a UE-AN RRC suspendresponse message (2030 a), which may include a cause code and a RRCresume ID. The value of the cause code may be the same as the cause codein step (2020 a). The AN 204 may then deactivate all AS signalingprocedures and mark all DRBs in a suspended state. Then, the UE 202 mayperform a UE RRC suspend procedure (2030 b).

Next, the AMF 218 and the SMF(s) 220 may perform an AMF-SMF UE CN-IDLEstate update procedure (2040). The AMF 218 may send to the SMF(s) 220 anAMF-SMF UE CN-IDLE state transition request message (2040 a), which maycontain the temp UE ID, the new CN-IDLE state of the UE 202, and theoptional cause code as in step (2020 a). Then, the SMF(s) 220 may sendto the AMF 218 an AMF-SMF UE CN-IDLE state transition response message(2040 b). By acknowledging the UE CN-IDLE state transition requestmessage received from the AMF 218, the SMF 220 may implicitly assumethat the AN 204 has placed all PDU sessions of the UE 202 in theSession-IDLE state.

Next, the SMF 220 may perform a SMF deactivate all sessions procedure(2050) to place the PDU sessions in the Session-IDLE state in the UPF(s)220. The SMF 220 may send to the UPF(s) 212 that serve the UE's PDUsession(s) a SMF-UPF deactivate all sessions request message (2050 a),which may indicate that the state of the PDU session is to be changed tothe Session-IDLE state. The message (2050 a) includes the temp UE ID andthe session ID(s) (or a wildcard parameter). The wildcard parameter(which may be a special value for a session ID) may indicate that thestate of the PDU sessions being served by the UPF 212 should be set to“Session-IDLE”. Then, the UPF 212 may set the field “Session-State” ofthe UE's PDU session context to Session-IDLE. The UPF 212 may follow theSM policy in the Keep-UE-Context-For-Idle-Sessions parameter. If in thisUPF 212, the UE 202 has no other active PDU session (served by otherRATs), and if the value of the Keep-UE-Context-For-Idle-Sessionsparameter is set to “Keep”, then the UPF 212 (and the SMF 220) may keepthe UE context regardless of session state. If in this UPF 212, the UE202 has no other active PDU session (served by other RATs), and if thevalue of the Keep-UE-Context-For-Idle-Sessions parameter is set to“Can-Be-Released”, then the UPF 212 may keep the complete UE context,depending on the storage resource.

Next, the UPF 212 may send to the SMF 220 a SMF-UPF deactivate allsessions response message (2050 b). If the UE context is released, thenthe UPF 212 may send to the SMF 220 the complete UE context, includingthe UE's SM context and the UE's charging context. It is noted that theUPF 212 may also send to the PCF 222 the UE charging context. If the UPF212 releases the UE context, then the SMF 220 may receive the completeUE context from the UPF 212 and may store the complete UE context inlocal memory. It is noted that the UPF's UE context and the SMF'scontext may have some common fields, such as the UE temp ID, the IPaddress(es), and the TFT. To save memory resources, the SMF 220 maystore only the additional UPF's UE context parameters that SMF's UEcontext does not have. Optionally, the SMF 220 may notify the AN 204that all PDU sessions are in the Session-IDLE state by sending a SMF-ANall session idle notification message (2050 c). Also optionally, the SMF220 and the UDM 216 may perform a SMF-UDM UE context update procedure(765), as described above. Next, the SMF 220 and the PCF 222 may performa SMF-PCF UE context update procedure (1580), that may include the UE CNstate and the state of sessions that change their session state. It isnoted that, optionally, the PCF 222 function may also access the UDM 216to obtain the UE context if the policy is to store the UE context in UDM216.

FIG. 21 illustrates, in a flowchart, an example of a method oftransitioning a session state (2100), in accordance with the RRC suspendprocedure (2000). The method (2100) is performed by the SMF 220. The SMF220 may be configured to receive from the AMF 218 the AMF-SMF UE CN-Idlestate transition request message (2040 a), as described above. The SMF220 may then send to the AMF 218 the AMF-SMF UE CN-IDLE state transitionresponse message (2040 b), as described above. Next, the SMF 220 maysend to the UPF 212 the SMF-UPF deactivate all session request message(2050 a), as described above. The SMF 220 then receives from the UPF 212the SMF-UPF deactivate all session response message (2050 b), asdescribed above. Next, the SMF 220 performs a SMF-PCF UE context updateprocedure (1580) with the PCF 222, as described above. Other steps maybe added to the method (2100), including the SMF optionally sending theSMF-AN all sessions idle notification message to the AN 204, andperforming the SMF-UDM UE context update procedure (765), as describedabove.

FIG. 22 illustrates, in a flowchart, an example of a method oftransitioning a session state (2200), in accordance with the RRC suspendprocedure (2000). The method (2200) is performed by the AN 204. The AN204 may be configured to determine to release a session (2210). Thedetermination (2210) may be based on receiving a UE-AN RRC suspendrequest message from the UE 202. Alternatively, the determination (2210)may also be based on the AN 204 detecting no activities in the UL andDL. Once the determination (2210) is made, the AN 204 may send theAN-AMF UE CN-IDLE state transition request message (1620 a) to the AMF218, as described above. The AMF 218 may then send the AN-AMF UE CN-IDLEstate transition response message (1620 b) to the AN 204, as describedabove. Next, the AN 202 may send the UE-AN RRC suspend response message(1630 a), as described above. Other steps may be added to the method(1800), including AN 204 receiving the SMF-AN all session idlenotification message (1650 c) from the SMF 220, as described above.

FIG. 23 illustrates, in a message flow diagram, an example of a RRCresume procedure (2300), in accordance with an embodiment of the presentinvention. The procedure (2300) may be triggered when the UE RRC is in aRRC-Suspended state and the UE 202 has data to send in the UL. Theprocedure (2300) is triggered when the UE 202 sends to the AN 204 aUE-AN RRC resume request message (2310). The message may include atleast the RRC resume ID. Optionally, the RRC resume request includes theDRB IDs or Session ID to be resumed. If the AN ID denotes the previous(former) AN 204′ when the RRC was suspended (note, the former AN ID isprovided in the RRC resume ID), then the new serving AN 204 and theformer AN 204′ perform a UE context handover procedure (2320) so thatthe new serving AN 204 can get the UE context from the former AN 204′.After sending the UE context to the new serving AN 204, the former AN204′ may release the UE context.

Next, the AN 204 and the AMF 218 perform an AN-AMF UE CN-CONNECTED statetransition procedure (2330). The AN 204 may check the UE context to findthe serving AMF 218. The AN 204 may send to the AMF 218 an AN-AMF UECN-CONNECTED state transition request message (2330 a). The message mayinclude the temp UE ID and the new CN-CONNECTED state. Next, the AMF 218may send to the AN 204 an AN-AMF UE CN-CONNECTED state transitionresponse message (2330 b). If the AMF 218 can support the UE 202, the UECN state transition response message may include an acknowledgement.Otherwise, the message may include a cause code.

It should be noted that if the RRC resume request in step (2310) doesnot include a DRB ID or Session ID, then the following AN-SMFSession-ACTIVE state transition procedure (2400) is not performed.Furthermore, if the CN-CONNECTED state transition response includes acause code, the UE 202 performs a re-attachment procedure and theprocedure (2400) and step (2380) are not performed. In step (2370), theRRC resume response may include the cause code generated by the AMF 218in step (2330 b). Moreover, if there are errors in step (2320) or(2330), the procedure (2400) and step (2380) are not performed and theUE 202 does not resume the RRC suspended connection. In step (2370), theAN 204 may send a cause code to the UE 202 so that the UE may initiate anew (re-)attach procedure (300).

The AN 204 may send, via the AMF 218, to the SMF 220 an AN-SMFSession-ACTIVE state transition request message (2340), which mayinclude the session ID(s), its new state Session-ACTIVE, the SM-NSSAI tobe recognized by AMF 218 for selecting the SMF, and the temp UE ID. Themessage may include a cause code “RRC Resumed by UE”. If the value ofthe Activate-Session-when-RRC-Resumed parameter is set to “Yes” for somePDU sessions, the AN 204 may include the session ID(s) of those PDUsessions in the Session-ACTIVE state transition request. In the casewhere the UE 202 is served by a new AN 204, the AN-SMF Session-ACTIVEstate transition request may also include an AN path switch requestmessage, which may include the IP address of the new serving AN 204.

Next, the SMF 220 and the UPF 212 may perform a SMF-UPF Session-ACTIVEstate transition procedure (2350). The SMF 220 may send to the UPF 212 aSMF-UPF Session-ACTIVE state transition request message (2350 a). Themessage may include the temp UE ID, the session IDs and the new stateSession-ACTIVE. If the UPF 212 has released the UE context, then the SMF220 may also send to the 212 UPF the previously stored UE context in theSMF-UPF Session-ACTIVE state transition request message. In the casewhere the UE 202 is served by a new AN 204, the SMF-UPF Session-ACTIVEstate transition request may also include the AN path switch request,which may include the IP address of the new serving AN 204. The UPF 212prepares its resources according to the UE context. If the resources atthe UPF 212 are ready, the UPF 212 may send to the SMF 220 a SMF-UPFSession-ACTIVE state transition response message (2350 b) with anacknowledgment. If the UPF 212 has enough resources to support theresumed session(s), then the session state in the UPF's 212 UE contextmay be changed to Session-ACTIVE. If the UPF 212 does not have enoughresources to support the resumed session(s), the Session-ACTIVE statetransition response message may include a cause code.

The SMF 220 may send to the AN 204 an AN-SMF Session-ACTIVE statetransition response message (2070), which may include the state of therequested session IDs. In its UE context, the AN 204 may change thesession state from Session-IDLE to Session-ACTIVE. For sessions that arenot activated due to errors in steps (2030) and (2050), the AN-SMFSession-ACTIVE state transition response may include a cause code.Optionally, the SMF 220 and the UDM 216 may perform a SMF-UDM UE contextupdate procedure (765), as described above.

The SMF 220 and the PCF 222 may perform a SMF-PCF UE context updateprocedure (1580). Next, the AN 204 may send to the UE 202 a UE-AN RRCresume response message (2370). The message may include either anacknowledgement or cause codes for the RRC resume request. The causecodes may indicate an error of the AN 204 (in step (2320)), the AMF (instep (2330), or the RRC resume errors. If in step (2310), the UE-AN RRCresume request included DRB IDs (or session IDs), the UE-AN RRC resumeresponse message may also include either an acknowledgement or causecode for each requested DRB IDs.

The UE 202 has UL data to send in the DRB that was requested in step(2310). The UE may send to the AN 204 the UL grant request message(2380). The AN 204 provides resources for the DRB in the UL. After that,the UE may send data over the DRB.

FIG. 24 illustrates, in a flowchart, an example of a method oftransitioning a session state (2400), in accordance with the RRC resumeprocedure (2300). The method (2400) is performed by the SMF 220. Themethod comprises the SMF 220 configured to receive from the AN 204, viathe AMF 218, the AN-SMF Session-ACTIVE state transition request message(2340), as described above. Next, the SMF 220 may send to the UPF 212the SMF-UPF Session-ACTIVE state transition request message (2350 a), asdescribed above. The SMF 220 then receives from the UPF 212 the SMF-UPFSession-ACTIVE state transition response message (2350 b), as describedabove. Next, the SFM 220 may send to the AN 204, via the AMF 218, theAN-SMF Session-ACTIVE state transition response message (2360), asdescribed above. Next, the SMF 220 performs a SMF-PCF UE context updateprocedure (1580) with the PCF 222, as described above. Other steps maybe added to the method (2400), including the SMF optionally performingthe SM-UDM UE context retrieval procedure, performing the SMF-UE contextupdate procedure (765), and receiving from the UE (via the AN 204) theUL grant request message, as described above.

FIG. 25 illustrates, in a flowchart, an example of a method oftransitioning a session state (2500), in accordance with the RRC resumeprocedure (2300). The method (2500) is performed by the AN 204. Themethod comprises the AN 204 receiving the UE-AN RRC resume request(2310) from a UE 202, as described above. Next, if the AN ID denotes aprevious AN 204′ (2510), then the serving AN 204 and the previous AN204′ perform the UE context handover procedure (2320), as describedabove. The AN 204 may send to the AMF 218 the AN-AMF UE CN-CONNECTEDstate transition request message (2330 a), as described above. The AN204 may then receive the AN-AMF UE CN-CONNECTED state transitionresponse message (2330 b) from the AMF 218. Next, the AN 204 may send tothe SMF 220, via the AMF 218, the AN-SMF Session-ACTIVE state transitionrequest message (2340), as described above. The AN 204 may then receivefrom the SMF 220, via the AMF 218, the AN-SMF Session-ACTIVE statetransition response message (2350), as described above. Next, the AN 204may send to the UE the UE-AN RRC resume response message, as describedabove. Other steps may be added to the method (2500), includingforwarding UL PDU transmissions received from the UE 202 to the UPF 212.

FIG. 26 illustrates, in a message flow diagram, an example of anindividual PDU Session-IDLE state transition procedure (2600) triggeredby the UE 202 or the AN 204, in accordance with an embodiment of thepresent invention. The UE 202 may have its own logic to determinewhether the state of RRC can be suspended to save energy, but withoutreleasing the current session(s). In this scenario, the state of thecurrent session(s) may be set to Session-IDLE in the AN 204, the UPF212, the SMF 220, the PCF 222, and optionally in the UDM 216. The UE 202may have multiple PDU sessions, where each session may be served by asingle UPF 212 or multiple UPFs 212. The UE 202 may have access tomultiple network slices, where each slice may have a separate SMF 220 toserve the UE 202. There is one-to-one mapping between the PDU session IDand the DRB ID.

The individual PDU Session-IDLE state transition procedure (2600) may betriggered by the UE 202 and by the AN 204. A first possible trigger forthe individual PDU Session-IDLE state transition procedure (2600) occurswhen the UE 202 sends to AN 204 a DRB-Suspend request message (2610 a).A second possible trigger for the individual PDU Session-IDLE statetransition procedure (2600) occurs when the AN 204, that is monitoringPDU session activities of all PDU sessions, detects no UL and DL packets(2610 b) of a session after Session-Monitor-Timeout timer. It is notedthat each PDU session may have a Session-Monitor-Timeout parameterconfigured by the PCF 222. The SMF 220 may obtain theSession-Monitor-Timeout parameter from the PCF 222 and send it to the AN204 during the session establishment procedure (700).

The AN 204 may send to the SMF 220 an AN-SMF Session-IDLE statetransition request message (2620), which may request to set a single ormultiple PDU sessions to the Session-IDLE state. The message (2620) mayinclude the temp UE ID, the SM-NSSAI(s), and the session ID(s). Aspecial value of a session ID (e.g., wildcard) may indicate that the PDUsessions being served by the same SM indicated in SM-NSSAI should be setto the idle state.

Next, the SMF 220 and the UPF(s) 212 may perform a SMF-UPF Session-IDLEstate transition procedure (2630). The SMF 220 may send to the UPF(s)212 that serve the PDU session(s) SMF-UPF Session-IDLE state transitionrequest message(s) (2630 a), indicating the Session-IDLE state of thePDU session(s). The message (2630 a) may include the temp UE ID and thesession ID(s). A special value of the session ID (e.g., wildcard) mayindicate that the state of the PDU sessions being served by the UPF 212should be set to “Session-IDLE”. Next, if there are UL or DL packets inthe UPF 212 buffer, the UPF 212 may send to the SMF 220 a SMF-UPFSession-IDLE state transition response message (2630 b) that may includea cause code. The state of the session remains Session-ACTIVE. If thereare no DL packets in the UPF 212 buffer, the UPF 212 may set the field“Session-State” of UE's PDU session context to Session-IDLE. The UPF 212may send to the SMF 220 a SMF-UPF Session-IDLE state transition responsemessage (2630 b) with an acknowledgement. If there are no more activesessions in the same UPF 212, the UE context could be released and theUPF 212 may send to the SMF 220 the complete UE context, including theSM context and the PCF context.

Next, the SMF 220 may send to the AN 204 an AN-SMF Session-IDLE statetransition response message (2640) (response to step (2620)). Themessage (2640) may include either an acknowledgement or the cause codein step (2630 b). If the UPF 212 releases the UE context, the SMF 220may receive the complete UE Context and the charging information fromthe UPF 212. The SMF 220 may store the complete UE context in a localmemory and forward the charging information to the PCF 222 as in step(2670) below. It is noted that the UPF's UE context and the SMF'scontext may have some common fields, such as the UE temp ID, the IPaddress(es), and the TFT. To save memory resources, the SMF 220 maystore only the UPF's UE context parameters that SMF's UE context doesnot have.

Next, the AN 204 and UE 202 may optionally perform an AN-UE DRB suspendprocedure (2650). The UE 202 may perform a UE DRB suspended procedure.After this step (2650), there may be no AS signaling for the suspendedDRB, and there may be no NAS signaling for PDU session associated withthe suspended DRB. Also optionally, the SMF 220 and the UDM 216 mayperform a SMF-UDM UE context update procedure (765), as described above.However, this step (765) may be mandatory if the SMF 220 releases the UEcontext. The SMF should then send all of the UE's UP context and theUE's SM context to UDM 216. Next, the SMF 220 and the PCF 222 mayperform a SMF-PCF UE context update procedure (1580), that may include aUE CN state, the state of sessions that change their session state, andcharging information. It is noted that, optionally, the PCF function 222may also access the UDM 216 to obtain the UE context if the policy is tostore the UE context in the UDM 216. It is further noted that the UPF212 may directly send to the PCF 222 the charging context.

FIG. 27 illustrates, in a flowchart, an example of a method oftransitioning a session state (2700), in accordance with the individualPDU Session-IDLE state transition procedure (2600). The method (2700) isperformed by the SMF 220. The method comprises the SMF 220 configured toreceive from the AN 204, via the AMF 218, the AN-SMF Session-IDLE statetransition request message (2620), as described above. Next, the SMF 220may send to the UPF 212 the SMF-UPF Session-IDLE state transitionrequest message (2630 a), as described above. The SMF 220 then receivesfrom the UPF 212 the SMF-UPF Session-IDLE state transition responsemessage (2630 b), as described above. Next, the SMF 220 may send to theAN 204, via the AMF 218, the AN-SMF Session-IDLE state transitionresponse message (2640), as described above. Next, the SMF 220 performsa SMF-PCF UE context update procedure (1580) with the PCF 222, asdescribed above. Other steps may be added to the method (2700),including the SMF optionally performing the SMF-UDF UE context updateprocedure (765), as described above.

FIG. 28 illustrates, in a flowchart, an example of a method oftransitioning a session state (2800), in accordance with the individualPDU Session-IDLE state transition procedure (2600). The method (2800) isperformed by the AN 204. The method comprises the AN 204 determiningthat a session state transition is to be performed (2810). Thedetermination (2810) may be made by the AN 204 receiving a UE-AN DRBsuspend request (2610 a), as described above. The determination (2810)may also be made by the AN 204 that is monitoring PDU session activitiesof all PDU sessions and detects no UL and DL packets (2610 b) of asession after Session-Monitor-Timeout timer, as described above. The AN204 then may send to the SMF 220, via the AMF 218, the AN-SMFSession-IDLE state transition request message (2620), as describedabove. Next, the AN 204 may receive from the SMF 220, via the AMF 218,the AN-SMF Session-IDLE state transition response message (2640), asdescribed above. Other steps may be added to the method (2800),including the AN performing the AN-UE DRB suspend procedure (2650), asdescribed above.

FIG. 29 illustrates, in a message flow diagram, an example of a PDUSession-ACTIVE state transition procedure (2900), in accordance with anembodiment of the present invention. The procedure (2900) is triggeredby a UE UL grant request when the UE 202 is in a RRC-CONNECTED state andhas UL data to be sent on a suspended DRB. The UE 202 may send to the AN204 a UE-AN UL grant request message (2910). The message may include theDRB ID(s). If a DRB is in a suspended state, then the UL grant requestmay imply a request to resume this DRB. If the sessions with sessionID(s) associated with the DRB ID(s) is(are) in a Session-IDLE state,then the procedure (2400) may be followed, as described above. Next, theAN 204 may send to the UE 202 a UE-AN UL grant response message (2920),which may include the DRB ID(s) or session ID(s), and either anacknowledgment or a cause code for each DRB. In the case of a cause codebeing included for a DRB, the UE 202 may request a new session when theCN 206 cannot resume the idle session. Upon receiving an acknowledgementfrom the AN 204 in the UE-AN UL grant response message (2920), the UE202 may send the UL packet to the AN 204 (2930) for the resumed DRB(s).The AN 204 may then forward UL packets (2930) to the UPF 212.

FIG. 30 illustrates, in a message flow diagram, an example of a PDUSession-ACTIVE state transition procedure (3000), in accordance with anembodiment of the present invention. In this scenario, the currentsession connection state is in the Session-IDLE state. The UPF 212 maynot have NG3 tunnel information in the UE context. The procedure (3000)may be triggered by the UPF 212 receiving a DL packet from a packet datanetwork (PDN) 208. The packet may be buffered in the UPF 212. Next, theUPF 212 may send to the SMF 220 a “Get UE Context Update” requestmessage to obtain the NG3 tunnel endpoint ID. Next, the SMF 220 checksthe state of the CN 206 in its UE context. If the UE 202 is in theCN-CONNECTED state, then the steps (3030 a), (3030 b), (3030 c) may notbe performed.

If the UE 202 is in the CN-IDLE state, the SMF 220 may send an “UpdateUE's CN State” request (3030 a) to the AMF 218 so that the AMF 218 maypage the UE paging function. The message (3030 a) may include the tempUE ID. Next the AMF 218 may perform a UE paging procedure (3030 b). Thismay involve a UE context handover procedure if the UE 202 is served by anew AN 204. If the AMF 218 successfully pages the UE 202, then the UEenters a CN-CONNECTED state. The AMF 218 may send to the SMF 220 an“Update UE's CN State” (3030 c) service, which indicates that the UE 202is in the CN-CONNECTED state.

Next, the SMF 220 may update the CN-CONNECTED state of the UE 202. TheSMF 220 may send to the AN 204 a Session-ACTIVE state transition request(3040) message. The message may include the temp UE ID, the session IDthe UE's PDU session context and the QoS profile. Next, the AN 204 mayestablish radio resources (3050) with the UE 202 for the PDU session.This step (3050) may include admission control, if required. Next, theAN 204 may send to the SMF 220 a Session-ACTIVE state transitionresponse (3060) message which may include the SM-NSSAI, the temp UE ID,the session ID, and either an acknowledgement or a cause code for thissession ID.

Next, the SMF 220 may send to the UPF 212 a “Get UE Context Update”service response (3070). If the SMF 220 received a cause code from theAMF 218, then the SMF 220 may send a cause code to the UPF 212 torelease the UE context and drop received packets. The SMF 220 may alsorelease the UE context. If the SMF 220 receives a cause code from the AN204, then the SMF 220 may send a cause code to the UPF 212. The UPF 212may then drop received packets. If the SMF 220 receives anacknowledgement in steps (3030) and (3060), then the SMF 220 may send tothe UPF 212 a “Get UE Context Update” response (3070) which may includethe UE ID, the session ID and the NG3 tunnel endpoint ID. Next, the SMF220 and the PCF 222 perform the SMF-PCF UE context update procedure(1580), as describe above. The SMF 220 may request the PCF 222 toperform an “Update UE Context” service where the new session connectionstate may be sent to the PCF 222. The service request from the SMF 220may include the UE ID, the session ID and the new session connectionstate.

FIG. 31 illustrates, in a flowchart, an example of a method ofperforming a Session-ACTIVE state transition (3100), in accordance withthe PDU Session-ACTIVE state transition procedure (3000). The method(3100) may be performed by the SMF 220. The SMF 220 may be configured toreceive a “Get UE Context Update” service request (3020) message fromthe UPF 212. The SMF 220 may send an “Update UE's CN State” servicerequest (3030 a) message to the AMF 218. Next, the SMF 220 may receivean “Update UE's CN State” service response (3030 c). Next, the SMF 220may send to the AN 204, via the AMF 218, a Session-ACTIVE statetransition request (3040) message. Next, the SMF 220 may receive fromthe AN 204, via the AMF 218, a Session-ACTIVE state transition response(3060) message. Next, the SMF 220 may send to the UPF 212 a “Get UEContext Update” service response (3070) message. Next the SMF 220 mayperform the SMF-PCF UE context update procedure (1580), as describedabove. Other steps may be added to the method (3100).

FIG. 32 illustrates, in a message flow diagram, an example of a PDUSession-ACTIVE state transition procedure (3200), in accordance with anembodiment of the present invention. The procedure (3200) is triggeredby a UPF 212 request when the PDU session is in the Session-IDLE state,and thus, the UPF 212 may not have the TFT for the DL packet of idlesessions. The UE's PDU context may be stored either in the SMF 220 orthe UPF 212. The UPF 212 receives a DL packet from a packet data network(PDN) 208 (3210). The packet may be buffered in the UPF 212. The UPF 212may send to the SMF 220 a UPF-SMF UE context request message (3220). Ifthe UPF 212 does not have the UE context, the UPF 212 may identify andsend the serving SMF 220 the UPF-SMF UE context request, which mayinclude the packet header information. It is noted that some applicationservers may set up a tunnel with the UPF 212. This tunnel may beassociated to sessions handled by a specific SMF 220. The UPF 212 mayrely on the tunnel information to identify the service SMF 220.

The SMF 220 may check the CN state in UE context. If the UE 202 is inthe CN-IDLE state (i.e., the UE 202 is in the RRC-IDLE state orRRC-Suspended state), then the SMF 220 may initiate a UE pagingprocedure (3230). The SMF 220 may send to the AMF 218 a SMF-AMF UEpaging request message (3230 a). The message may include the temp UE ID.The AMF 218 may then perform a UE paging procedure (3230 b). This stepmay involve a UE context handover procedure if the UE 202 is served by anew AN 204. If the AMF 218 successfully pages the UE 202, then the UE202 enters the CN-CONNECTED state. The AMF 218 may send to the SMF 220 aSMF-AMF UE paging response message (3230 c), which may indicate that theUE 202 is in the CN-CONNECTED state.

The SMF 220 may update the UE 202 to be in the CN-CONNECTED state. TheSMF 220 may send to the AN 204 a SMF-AN Session-ACTIVE state transitionrequest message (3240). The message may include the temp UE ID, thesession ID, and the Session-ACTIVE state parameter. Optionally, if theDRB is currently suspended, the AN 204 initiates an AN-UE DRB resumeprocedure (3224). The AN 204 may send to the UE 202 an AN-UE DRB resumerequest message (3224 a). The message may include the DRB IDs. Then, theUE 202 resumes the suspended DRB. The UE 202 may send to the AN 204 anAN-UE DRB resume response message (3224 b), which may include the DRBID, and either an acknowledgment or a cause code. It is noted that instep (3224 a), the AN-UE DRB resume request message may be implicitlycarried in a DL channel grant message.

The AN 204 may send to the SMF 220 a SMF-AN Session-ACTIVE statetransition response message (3260), which may include the SM-NSSAI, thetemp UE ID, the session ID, and either an acknowledgement or a causecode for this session ID. If the SMF 220 receives a cause code from theAN 204, the SMF 220 may initiate the SM establishment procedure (700)triggered by the CN 206. Otherwise (the SMF 220 receives anacknowledgment from the AN 204), the SMF 220 may send to the UPF 212 aUPF-SMF UE context response message (3270), which may include aSession-ACTIVE state confirmation. If the UPF 212 does not have the UEcontext, the message may also include a complete UE context. The UPF 212may setup UP resources to support the PDU sessions. Optionally, the SMF220 and the UDM 216 may perform a SMF-UDM UE context update procedure(765), as described above. The SMF 220 and the PCF 222 may perform aSMF-PCF UE context update procedure (1580). The UPF 212 may then send DLpacket to the UE 202 (3280).

FIG. 33 illustrates, in a flowchart, an example of a method oftransitioning a session (3300), in accordance with the PDUSession-ACTIVE state transition procedure (3210). The method comprisesthe SMF 220 configured to receive the UPF-SMF UE context request message(3220), as described above. Next, the SMF 220 may send to the AN 204,via the AMF 218, the SMF-AN Session-ACTIVE state transition request(3240), as described above. Next, the SMF 220 may receive from the AN204, via the AMF 218, the SMF-AN Session-ACTIVE state transitionresponse message (3260), as described above. Next, the SMF 220 may sendto the UPF 212 the UPF-SMF UE context response message (3270), asdescribed above. Next, the SFM 220 may perform a SMF-PCF UE contextupdate procedure (1580), as described above. Other steps may be added tothe method (3300), including the SMF 220 performing the SFM-UDM UEcontext retrieval procedure with the UDM 216, the SMF 220 initiating theUE paging procedure, and the SMF 220 performing the SMF-UDM UE contextupdate procedure with the UDM 216, as described above.

FIG. 34 illustrates, in a component diagram, an example of an “UpdateUE's CN State” service procedure (3400). The AMF 218 may provide aservice to page the UE 202 when the UE 202 is in the CN-IDLE state. TheAMF 218 may maintain the UE context. A requester 3405 may send an“Update UE's CN State” request (3410) message to the AMF 218. Themessage may include the UE ID. The requester 3405 may be the SMF 220 asin step (3030 a) above. The requester 3405 may also be any networkfunction that may communicate with the AMF 218. Next, the AMF 218 maysend to the requester 3405 an “Update UE's CN State” response (3420)message, which may include an acknowledgement of the UE's CN-CONNECTEDstate and the IP address of the AN 204. If a paging failure occurs, theresponse may include a cause code.

FIG. 35 illustrates, in a component diagram, an example of a “PDUSession Modification” service procedure (3500). This service (3500)provides the PDU session modification service such as QoS parameters andcharging parameters. The SMF 220 may maintain the UE context. Arequester 3505 may send a “Session Modification” request (3510) messageto the SMF 220. The message may include the UE ID, the PDU session IDand the new session parameters. The requester 3505 may be any networkfunction that may communicate with the SMF 220. Next, the SMF 220 maysend to the requester 3505 a “Session Modification” response (3520)message to confirm the completion of the service. The message (3520) mayinclude an acknowledgement or a cause code.

FIG. 36 illustrates, in a component diagram, an example of a “Get UEPolicies” service procedure (3600). The PCF 222 may provide UE policiesto a requester 3605. The PCF 222 may have policies for services, DN 208,time zone, and UE 202. A requester 3605 may send a “Get UE Policies”request (3610) message to the PCF 222. The message may include the typeof PDU session, the DN name, the time zone of the UE 202, and therequested policy such as the SM policy, the access and mobility (AM)policy, the QoS policy and the charging policy. The requester 3605 maybe any network function that may communicate with the PCF 222. Next, thePCF 222 may send to the requester 3605 a “Get UP Policies” response(3620) message, which may include the requested policy.

FIG. 37 illustrates, in a component diagram, an example of an “Update UEContext” service procedure (3700). The PCF 222 may provide an update UEcontext service to the requestor 3605 for some scenarios, includingdynamic policy. The PCF 222 may have policies for services, the DN 208,the time zone and the UE 202. A requester 3605 may send an “Update UEContext” request (3710) message to the PCF 222. The message may includethe UE ID, the session ID(s), and a list of parameters and theircorresponding new values. The requester 3605 may be the SMF 220 as instep (1580) above. The requester may also be any network function thatmay communicate with the PCF 222. Next, the PCF 222 may store new valuesof the parameters to the UE context. The PCF 222 may send to therequester 3605 an “Update UE Context” response (3720) message to confirmthat the service has been performed or to report an error (via a causecode).

FIG. 38 illustrates, in a component diagram, an example of an “Update UEContext” service procedure (3800). When a PDU session has beenestablished, the UPF 212 may have the UE context. A requester 3805 maysend to UPF(s) 212 that serve the PDU session an “Update UE Context”request (3810) message. The message may include the UE ID, the sessionID(s) and a list of parameters and their corresponding new values. Thenew value may be the NULL value. If a new tunnel endpoint ID is NULL,the UPF 212 may contact the SMF 220 if the UPF 212 does not know how toforward the packet. The requester 3805 may be the SMF 220 as in step(3070) above. The requester 3805 may also be any network function thatmay communicate with the UPF 212. The UPF 212 may receive new sessionparameters, and check whether the new parameters may be supported. Ifthe new parameters may be supported, then the UPF 212 may reconfigure orrelease it resources tat serve the PDU session. The UPF 212 may send tothe SMF 220 the SMF-UPF session modification response (3820) messagethat may include an acknowledgement to confirm that the service has beenperformed or to report an error (via a cause code).

FIG. 39 is a call flow diagram 3900 illustrating methods that can becarried out at a series of different nodes and functions for aSession-IDLE State Transition of a UE under a CM_Connected mode. Asshown in FIG. 39, there can be a number of different triggers for thestart of the session Connection State Transition procedure. Asillustrated in FIG. 39, a UE 202 or an AN 204 can request the sessionIDLE transition. Those skilled in the art will appreciate that othertriggers may be applicable as well. Either the UE 202 or the AN 204, canissue a session IDLE transition request (at 3902 a and 3902 b) towardsthe SMF 220. In some examples, the request message can include the UETemp ID, the Session ID(s), a Session-IDLE state, or an AD ID asappropriate. There may be a difference in the information includedwithin the message depending on the node or function that initiates themessage. A special value of the Session ID (e.g. wildcard) can be usedto denote all of the PDU sessions that meet the identifying requirementsincluded within the request. It should also be understood that the SMF220 may initiate the session_idle state transition either in response toanother external trigger, or in response to an internal condition beingsatisfied. The SMF 220 and UPF 212 communicate with each other toperform a session update. The SMF 220 can transmit a session UpdateRequest (e.g. an N4 Session update request) 3904 a towards the UPF 212.This request may serve as a request to the UPF 212 to release NG3information associated with an AN from the UE's PDU session context (asidentified by the UPF). This session information may include the tunnelendpoint ID of AN 204 and the AN IP address. In response to thisrequest, the UPF 212 can release the session and transmit an reply 3904b to the SMF 220 to confirm the completion of UE Context Update request.The SMF 220 can then send a session update request 3906 towards the AN204, which may optionally be routed through the AMF 218. In someembodiments, this may take the form of an N2 session update request sentto the AN 204 via the AMF 208. The session update request can includeinformation such as UE Temp ID, Session ID(s) and Session-IDLE state. Inresponse to receipt of the session update request, the AN 204 and the UE202 can perform an RRC Connection Reconfiguration procedure 3908 torelease allocated resources for the session(s). The AN 204 can informthe UE 202 of the session state transition via the procedure. Thoseskilled in the art will appreciate that there may be further details tothe interaction of the UE 202 and AN 204, but these implementationdetails may vary from solution to solution. Upon release of the contextof the PDU session (or sessions), the AN 204 can send a response 3910 tothe Session Update Request (a Session Update Response, such as an N2Session Update Response). This response can be sent towards the SMF 220,and may optionally be sent through the AMF 208. The response may serveto confirm the completion of Session-IDLE state transition in the UE202, and may include the UE Temp ID and Session ID. At this point, theSMF 220 may set the session connection state (at 3912) of the UE contextto the Session-IDLE. Those skilled in the art will appreciate that otherservices may be called upon to transfer the session update request andresponse without departing from the intended method. It should also beunderstood that a Policy Control Function may be involved as well.

FIG. 40 is a call flow diagram illustrating methods that can be carriedout at a series of different nodes and functions for a Session-ACTIVEState Transition Triggered by UE under CM_Connected mode. As shown inthe embodiment of FIG. 40, As shown in FIG. 40, the method can beinitiated by a UE 202 transmitting, towards the SMF 220, a request for atransition to an active session. As shown in FIG. 40, step 4002, the UE202 sends to the SMF 220 (optionally via the AMF 218) a Session-ACTIVErequest. The message can include the UE Temp ID, Session ID(s), andSession-ACTIVE state. It should be understood that a special value ofSession ID (e.g. wildcard) can be used to denote all of the PDU sessionsthat satisfy other conditions specified in the request. In response, theSMF 220 can send (at 4004) a session update request, such as an N2Session Update Request, towards the AN 204, e.g. via the AMF. 218 Thesession update request message may include a UE Temp ID, a Session ID, aSession-ACTIVE state, and NG3 connection information. The AN 204 and theUE 202 can perform an RRC Connection Reconfiguration procedure (at4006). In one embodiment, the RRC connection reconfiguration proceduremay include the AN 204 assigning radio resources to serve the PDUsession according to a QoS profile. If the QoS profile requiresadmission control, the AN 204 can perform admission control (or caninvoke an admission control procedure). If there are insufficient radioresources to satisfy the needs of the PDU session, or if the AN 204cannot otherwise support the session, the AN 204 can instruct orotherwise inform the UE 202 to release the PDU session. If there aresufficient radio resources, and the AN 204 can otherwise support thesession, the AN 204 can send an RRC Connection Reconfiguration messageto the UE 202 that indicates the radio resource allocation. Inaccordance with the RRC connection configuration, the UE 202 can set thesession connection state to Session-ACTIVE. It will be understood bythose skilled in the art that other steps may be taken as paert of theRRC connection reconfiguration. The addition of these steps may varyfrom implementation to implementation and are thus not discussed herein.Upon configuring (or reconfiguring as the case may be) the RRCconnection, the AN 204 can send a session update response message (at4008) towards the SMF 220. Optionally this message may be sent to theAMF 218 for delivery to the SMF 220. In some embodiments, the messagemay be an N2 Session Update Response. The message can include the UETemp ID and Session ID. The AN 204 may use this response message 4008 tonotify the SMF 220 of either the successful completion of Session-ACTIVEstate transition or a cause code associated with a failure tosuccessfully complete the transition, e.g. lack of radio resources forto support the PDU session. If the SMF 220 is notified of a successfulcompletion of the transition, it may transmit a request to the UPF 212to update the UE session context. This may take the form of messages4010 a and 4010 b in response. If the SMF 220 is not notified of asuccess (including the scenario in which it is notified of a failure)steps 4010 a and 4010 b may be omitted. As shown in 4010 a, the SM 220can transmit a request to the UPF 212 to update session information.This may take the form of a N4 session Update Request sent to the UPF212 requesting the update of NG3 information associated with the AN 204that is associated with the UE's PDU session context in UPF 212. Therequest message may include UE Temp ID, Session ID, and NG3 information,including the tunnel endpoint ID of AN and the AN IP address. Inresponse, the UPF 212 can transmit a confirmation as shown in 4010 b.This confirmation may take the form of an N4 Session update Response.If, the SMF 220 receives an indication from the AN 204 that the RRCconnection reconfiguration was successful, the SMF 220 may set thesession connection state (at 4012) in the UE context accordingly. If thesession connection state transition is successful, the SMF 220 can setthe session connection state to the Session-ACTIVE. If the sessionconnection state transition is unsuccessful (e.g. the AN cannot supportthe PDU Session), the SMF 220 may initiate a Session Release procedure.As noted above, with respect to FIG. 39, the PCF may be involved duringthe session connection state transition procedures. It should also beunderstood that different services may be involved in the transfer of N2messages.

The procedure of releasing a NAS signalling connection may be initiatedby a 5G (R)AN 204 node or the AMF 218. The AMF 218 may inform the SMF220 that the UE 202 enters CM-IDLE state so that the SMF 220 may informthe UPF(s) 212 to deactivate existing PDU sessions by releasing the N3tunnel information (including (R)AN IP address and tunnel endpointidentifier) of UE context at the UPF 212. The UE 202 may consider theNAS signalling connection released if the UE detects the RRC connectionis released. After the NAS signalling connection is released, the UE 202and the AMF 218 may enter the CM-IDLE state.

When a UE 202 has multiple established PDU sessions, the activation ofUP connections of the existing PDU sessions may cause a UE-CN user planeconnection (i.e., data radio bearer and N3 tunnel) for a PDU session tobe activated. For the UE 202 in the CM-IDLE state, either the UE 202 ora network-triggered service request procedure may support independentactivation of UP connection of existing PDU session. For the UE 202 inthe CM-CONNECTED state, independent activation and deactivation of UPconnections of existing PDU sessions may be supported.

There may be different types of PDU session establishment procedures.One type of session establishment procedure may be a UE 202 initiatedPDU session establishment procedure. Another type of sessionestablishment procedure may be a network initiated PDU sessionestablishment procedure. In the case of a network initiated procedure,the network may send the device trigger message to the application(s) onthe UE side. The trigger payload included in a device trigger requestmessage may include information on which application on the UE side isexpected to trigger the PDU session establishment request. Based on thatinformation, the application(s) on the UE side trigger the PDU sessionestablishment procedure.

There may be different embodiments of PDU session deactivation. One typeof session deactivation procedure may be that all PDU sessions of the UE202 may be deactivated when the UE's CM state transits from theCM-CONNECTED state to the CM-IDLE state. Another type of sessiondeactivation procedure may be the (R)AN 204 initiating all PDU sessiondeactivation. The (R)AN 204 may inform the AMF 218 of the cause of the aRRC release, such as O&M intervention, unspecified failure, userinactivity, repeated RRC signalling integrity check failure, release dueto UE 202 generated signalling connection release, etc. Another type ofsession deactivation procedure may be the AMF 218 initiating all PDUsession deactivation due to authentication failure. Another type ofsession deactivation procedure may include the (R)AN 204 initiating aselective PDU session deactivation. The (R)AN 204 may inform the SMF220, via the AMF 218, of the cause of the selective PDU session such asO&M intervention and user inactivity.

A procedure may be used to release a N2 connection and at the same timedeactivate PDU sessions when the UE 202 enters the CM-IDLE state. FIG.41 illustrates, in a message flow diagram, an example of a PDU sessiondeactivation procedure (4100), in accordance with an embodiment of thepresent invention. The UE 202 and (R)AN 204 may perform a RRC Release(600A). If the RRC connection is released, the (R)AN 204 may interactwith the UE 202 to release the RRC signalling connection. The UE 202enters the CM-IDLE state and all PDU sessions may be deactivated. Thus,the UE 202 knows that the release of RRC implies deactivation of PDUsessions. Next, the (R)AN 204 may send (N2 message) a RRC ReleaseNotification (4102) to the AMF 218. The message (4102) may include acause code, such as O&M intervention, UE inactivity, etc. It is notedthat in certain scenarios, step (600A) may be initiated before or inparallel with step (4102).

Next, the (R)AN 204 may create (N11 message) one or more N2 ReleaseNotification message and send them (4104) via AMF 218 to the SMF(s) 220that serve the PDU sessions to be deactivated. The message (4104) mayinclude a UE ID to identify the UE (such as temporary UE ID or SUPI), alist of PDU session ID(s) to be deactivated, and a cause code.Alternatively, the message (4104) includes a UE ID to identify the UE(such as temporary UE ID or SUPI), the (R)AN information, list of PDUsession ID(s) to be deactivated, PDU session ID and cause code. The(R)AN information indicates the (R)AN's IP address that releases the RRCconnection. Next, the SMF 220 may send (N4 message) a N3 Release Request(4106) to the UPF(s) 212. The message (4106) may include a UE ID (suchas temporary UE ID or SUPI) to identify the UE, and PDU session ID(s) tobe deactivated. Next, the UPF 212 may drop all remaining packets ofdeactivated PDU sessions, if any. The UPF 212 may release the N3 tunnelinformation (such as (R)AN IP address and tunnel endpoint identifier) inthe UE's PDU session context of PDU sessions to be deactivated. The UPF212 may send (N4 message) a N3 Release Response (4108) to the SMF 220confirming the release of N3 tunnel information.

The SMF 220 may send (N11 message) a N2 Release NotificationAcknowledgment (4110) to the AMF 218 to confirm the receipt of the AMF's218 notification (4104). The message (4110) may be sent before, after orin parallel with message (4106). Next, the AMF 218 may collect all theresponses from the SMF(s) 220 that were notified (in step (4104)). Onceall the acknowledgments from the SMF 220 are collected, the AMF 218 maysend (N2 message) a N2 Release Request (4112) to the (R)AN 204 with acause code. If step (600A) was not previously performed in the firststep of the procedure (4210), the (R)AN 204 and UE 202 may perform theRRC Release procedure (600A). The (R)AN 204 may request the UE 202 torelease the RRC connection. The UE 202 enters CM-IDLE state and all PDUsessions in the UE 202 may be deactivated. Upon receiving the RRCconnection release confirmation from the UE 202, the (R)AN 204 removesthe UE context.

Next, the (R)AN may send (N2 message) a N2 Release Response (4114) tothe AMF 218. This message (4114) is to provide confirmation for step(4112). Upon receiving the N2 Release Response message (4114), the AMF218 may set CM-IDLE state in the UE context and release the UE's N2connection. Next, the AMF 218 may send (N11 message) a N2 ReleaseConfirmation (4116) to the SMF(s) 220 to confirm the release of the N2connection. Alternatively, the message (4116) may be omitted.

In another embodiment, if the RRC Release procedure (600A) has beenperformed in the first step of the procedure (44100), the messages4112,4114, and procedure RRC Release (600A) between steps that messages4112 and 4114 may be omitted.

FIG. 42 illustrates, in a flowchart, an example of a method of releasinga N2 connection and deactivating a PDU session (4200), in accordancewith the N2 Release and PDU Session Deactivation procedure (4100). Themethod (4200) may be performed by the AMF 218. The method (4200)comprises the AMF 218 configured to receive a RRC Release Notificationmessage (4102). Next, the AMF 218 sends a N2 Release Notificationmessage (4104) to the SMF 220. Next, the AMF 218 receives a N2 ReleaseNotification Acknowledgment message (4110) from the SMF 220. Next, theAMF sends a N2 Release Request message (4112) to the (R)AN 204. Next,the AMF 218 receives a N2 Release Confirmation message (4114) from the(R)AN 204. Other steps may be added to the method (4200).

FIG. 43 illustrates, in a flowchart, another example of a method ofreleasing a N2 connection and deactivating a PDU session (4300), inaccordance with the N2 Release and PDU Session Deactivation procedure(4100). The method (4300) may be performed by the SMF 220. The method(4300) comprises the SMF 220 configured to receive a N2 ReleaseNotification message (4104) from the AMF 218. Next, the SMF 220 sends aN3 Release Request message (4106) to the UPF 212. Next, the SMF 220receives a N3 Release Response message (4108) from the UPF 212. Next,the SMF 220 sends a N2 Release Notification Acknowledgment message(4110) to the AMF 218.

A procedure may be used to release a N2 connection when the UE 202enters the CM-IDLE state or to deactivate PDU sessions when the (R)AN204 triggers selective PDU session deactivation. FIG. 44 illustrates, ina message flow diagram, an example of a PDU session deactivationprocedure (4400), in accordance with an embodiment of the presentinvention. The UE 202 and (R)AN 204 may perform a RRC Release procedure(600A) or a RRC Reconfiguration procedure (600B). If the RRC connectionis released, the (R)AN 204 may interact with the UE to release the RRCsignalling connection (procedure 600A). The UE enters CM-IDLE state andall PDU sessions are deactivated. If some PDU sessions are deactivated,then the (R)AN 204 may interact with the UE 202 to release DRB(s)belonging to the deactivated PDU sessions (procedure 600B). The UE 202may know that the release of all DRBs belonging to a PDU session impliesthe deactivation of corresponding PDU sessions. The (R)AN may send (N2message) a PDU Session Deactivation Request (4402) to the AMF 218. Themessage (4402) may include a PDU session ID(s), and a cause code. Thecause code may be RRC release with a reason, such as O&M intervention,UE inactivity, etc. The cause code may also be PDU session inactivity.In the case of a RRC release, the PDU session deactivation request doesnot include a PDU session ID. In the case of PDU Session inactivity, thePDU session deactivation request (4402) may include a list of PDUsession ID(s). It is noted that in certain scenarios, step (600A or600B) may be initiated before or in parallel with step (4402).

Next, the AMF 218 may create (N11 message) one or more PDU SessionDeactivation Request(s) and send them to the SMF(s) 220 that serve thePDU sessions to be deactivated (4404). The message (4104) may include anUE ID to identify the UE (such as temporary UE ID or SUPI), a list ofPDU session ID(s) to be deactivated, and a cause code. Next, the SMF 220may send (N4 message) a N3 Release Request (4106) to the UPF(s) 212. Themessage (4106) may include a UE ID (such as temporary UE ID or SUPI) toidentify the UE 204, and PDU session ID(s). The UPF 212 may release theAN N3 tunnel information (i.e., (R)AN IP address and tunnel ID) in theUE's PDU session context of PDU sessions to be deactivated. The UPF 212may send (N4 message) a N3 Release Response (4108) to the SMF 220confirming the release of the N3 tunnel information.

Next, the SMF 220 may send (N11 message) a PDU session deactivationresponse (4406) to the AMF 218 to confirm the release of the N3 tunnelinformation in UPF(s) 212. Next, the AMF 218 may collect all theresponses from the SMF(s) 220 that were requested to deactivate PDUsessions (in step (4404)). Once all the responses from the SMF 220 arecollected, the AMF 218 may send (N2 message) a PDU Session ConnectionRelease request (4408) to the (R)AN 204. In the case of the (R)AN 204 orAMF 218 initiated the deactivation of all PDU sessions, the message(4408) may include an indication to release the UE context (i.e., all UE204 related information, including N3 tunnel information and N2connection). If the case of selective PDU session deactivation, themessage (4408) may include a list of PDU session IDs.

If step (600A or 600B) was not previously performed in the first step ofthe procedure (4400), the (R)AN 204 and UE 202 may perform the RRCRelease (600A) or RRC reconfiguration procedure (600B). If the messagein step (4408) included an indication to release the UE context, the(R)AN 204 may request the UE 202 to release the RRC connection (600A).The UE 202 enters CM-IDLE state and all PDU sessions in the UE 202 maybe deactivated. Upon receiving the RRC connection release confirmationfrom the UE 202, the (R)AN 204 removes the UE context. If the message instep (4408) included an indication to deactivate a list of PDU sessions,the (R)AN 204 and UE perform a DRB release procedure (600B). The UEknows that the release of all DRBs belonging to a PDU session impliesthe deactivation of a corresponding PDU session. Upon receivingconfirmation for DRB release from the UE 202, the (R)AN 204 removes theUE's PDU session context of deactivated PDU sessions.

Next, the (R)AN 204 may send (N2 message) a PDU Session ConnectionRelease Response (4410) to the AMF 218. The message (4410) providesconfirmation for step (4408). If the message in step (4408) indicatedthe release of the UE context, the AMF 218 may set CM-IDLE state in theUE context and release the UE's N2 connection. Next, the AMF 218 maycreate (N11 message) a PDU Session Deactivation Confirmation and send it(4412) to the SMF(s) 220 to confirm the deactivation of PDU sessions(s)at the (R)AN 204.

FIG. 45 illustrates, in a flowchart, an example of a method ofdeactivating a PDU session (4500), in accordance with the PDU sessiondeactivation procedure (4400). The method (4500) may be performed by theAMF 218. The method (4500) comprises the AMF 218 configured to receive aPDU Session Deactivation Request message (4402) from the (R)AN 204.Next, the AMF 218 may send a PDU Session Deactivation Request message(4404) to the SMF 220. Next, the AMF 218 may receive a PDU SessionDeactivation Response message (4406) from the SMF 220. Next, the AMF 218may send a PDU Session Connection Release message (4408) to the (R)AN204. Next the AMF 218 may receive a PDU Session Connection Releaseresponse message (e) from the (R)AN 204. Next, the AMF 218 may send aPDU Session Deactivation Confirmation message (4412) to the SMF 220.Other steps may be added to the method (4500).

FIG. 46 illustrates, in a flowchart, another example of a method ofdeactivating a PDU session (4600), in accordance with the PDU sessiondeactivation procedure (4400). The method (4600) may be performed by theSMF 220. The method (4600) comprises the SMF 220 configured to receive aPDU Session Deactivation Request message (4404) from the AMF 218. Next,the SMF 220 sends a N3 release request message (4106) to the UPF 212.Next, the SMF 220 receives a N3 release response message (4108) from theUPF 212. Next, the SMF 220 sends a PDU session deactivation responsemessage (4406) to the AMF 218. Next, the SMF 220 receives a PDU sessiondeactivation confirmation message (4412) from the AMF 218. Other stepsmay be added to the method (4600).

A service request procedure may be used by a 5G UE 204 in the CM-IDLEstate to request the establishment of a secure connection to an AMF 218.The UE 202 in the CM IDLE state may initiate the service requestprocedure in order to send uplink signalling messages, user data, orresponse to a network paging request. After receiving the servicerequest message, the AMF 218 may perform authentication, and the AMF 218may perform the security procedure. After the establishment of a securesignalling connection to an AMF 218, the UE 202 or network may sendsignalling messages, e.g., PDU session establishment from UE 202 to thenetwork, or the SMF 220, via the AMF 218, may start the user planeresource establishment for the PDU sessions requested by network and/orindicated in the service request message. When the UE 202 is in theCM-CONNECTED state, the UE 202 may use another SM procedure to requestuser plane resource establishment for inactive PDU sessions.

FIG. 47 illustrates, in a message flow diagram, another example of asession-ACTIVE state transition procedure (4700), in accordance with anembodiment of the present invention. The UE 202 may send, in a N1message, a SM Session Activation Request (4702) to the SMF 220. Themessage (4702) may include PDU Session ID(s) to be activated. Themessage (4702) may not need to include the list of PDU sessionsavailable in the UE 202. The list of PDU sessions available in the UE202 may be included if the UE 202 has released some PDU sessions but notinformed the SMF 220. The (R)AN 204 may forward the N1 message SMSession Activation Request to the AMF 218 over the N2 interface. The(R)AN 204 does not need to include the UE 202 location, RAT type, and 5GUE temporary ID to the AMF 218. The AMF 218 may select the SMF 220 basedon the PDU session ID and forward the SM session activation request(4704) to the serving SMF 220 over the N11 interface. The forwardedmessage (4704) may include an UE ID to identify UE, such as 5G temporaryUE ID or SUPI, and PDU session ID(s).

The SMF 220 may use a “Message Transfer” service provided by the AMF 218to send a N11 message (4706), which contains one N2 SM Information to besent to the (R)AN 204 and one N1 SM Session Activation Accept NASmessage to be sent to the UE over the N11 interface. The N11 message mayinclude an UE ID to identify UE (such as 5G temporary UE ID or SUPI) andPDU Session ID(s). N2 SM Information message may include, PDU sessionID(s), and the UE's PDU session context (QoS profile and UPF 212terminating N3 tunnel information (UPF IP address and tunnel endpointidentifier)). Next, the AMF 218 may read the UE ID (such as 5G temporaryID or SUPI) and PDU session ID(s) to find the (R)AN 204. The AMF 218transfers the content of N11 message (4706), which contains N2 SMInformation and N1 SM Session Activation Accept NAS message receivedfrom the SMF in N2 message 4708 to the (R)AN over the N2 interface.Next, the (R)AN 204 and UE 202 may perform a RRC ConnectionReconfiguration procedure (600B) according to the QoS profile for allthe QoS flows of the PDU session activated provided in the N2 SMInformation. If the (R)AN 204 can support the PDU session, the RRCconnection reconfiguration message sent from the AN 204 to the UE 202may indicate radio resource allocation for the PDU session(s); and the(R)AN 204 forwards the N1 SM Session Activation Accept NAS messageprovided in message (4708) to the UE. After the user plane radioresources are setup, the uplink data from the UE 202 can now beforwarded (4710) to the RAN 204. The 5G RAN 204 may send the uplink data(4710) to the UPF 212 address and tunnel ID provided in step (4706).

Next, the (R)AN 204 may send (N2 message) an N3 (R)AN Information (4712)to the SMF 220 via the AMF 218. The message (4712) may include the PDUsession ID(s), a RAT type, a list of accepted QoS flows and a list ofrejected QoS flows for the corresponding activated PDU session, and(R)AN N3 tunnel information ((R)AN IP address and tunnel ID). Next, theAMF 218 transfers (N11 message) the N3 (R)AN Information (4714) to theSMF 220 by reading the PDU session ID(s) over the N11 interface. Themessage (4714) may include the an UE ID to identify the UE (such as 5Gtemporary ID or SUPI), PDU session ID(s), the RAT type, a list ofaccepted QoS flows and a list of rejected QoS flows for thecorresponding activated PDU session, and a (R)AN N3 tunnel information((R)AN IP address and tunnel ID). Optionally, if dynamics PCC isdeployed, the SMF 220 may initiate IP-CAN session modification (4716)and provide new location information of the UE 202 to the PCF 222.

In another embodiment, the (R)AN 204 can include the SMF Identifier inthe message (4712). The AMF 218 may read the SMF ID, not the PDUSSession ID(s), in order to forward the (N2 message) N3 (R)AN Information(4714) to the SMF 220.

If in step (4712), the AN 204 notifies successful completion of asession activation, then the SMF 220 requests the UPF 212 to update theUE's PDU session context. In this case, the SMF 220 may send a N4message Session Update Request (4718) to the UPF 212 to update N3 tunnelinformation of the (R)AN 204. The message (4718) may include an ID toidentify UE (such as 5G temporary ID or SUPI), PDU session ID(s), and(R)AN tunnel information (IP address of the (R)AN 204 and N3 tunnelendpoint ID). Next, the UPF 212 may send a N4 message Session UpdateResponse (4720) to the SMF 220 to confirm the completion of the sessionupdate request.

FIG. 48 illustrates, in a flowchart, an example of a method oftransitioning a session (4800), in accordance with the session-ACTIVEstate transition procedure (4700) of FIG. 47. The method (4800) may beperformed by the AMF 218. The method (4800) comprises the AMF 218configured to receive a SM Session Activation Request message (4702)from the UE 202, via the AN 204. Next, the AMF 218 sends a SM SessionActivation Request message (4704) to the SMF 220. Next, the AMF 218receives a N11 message containing N2 SM Information and N1 SM SessionActivation Accept (4706) from the SMF 220. Next, the AMF 218 sends a N2message containing N2 SM Information and N1 SM Session Activation Accept(4708) to the AN 204. Next, the AMF 218 receives a N3 (R)AN Informationmessage (4712) from the AN 204. Next, the AMF 218 sends a N3 (R)ANInformation (4714) to the SMF 220. Other steps may be added to themethod (4800).

FIG. 49 illustrates, in a flowchart, an example of a method oftransitioning a session (4900), in accordance with the session-ACTIVEstate transition procedure (4700) of FIG. 47. The method (4900) may beperformed by the SMF 220. The method (4900) comprises the SMF 220configured to receive a SM Session Activation Request message (4704)from the AMF 218. Next, the SMF 220 sends a N11 message containing N2 SMInformation and N1 SM Session Activation Accept (4706) to the AMF 218.Next, the SMF 220 receives a N3 (R)AN Information message (4714) fromthe AMF 218. Next, the SMF 220 may optionally perform a IP-CAN sessionmodification (4716) with the PCF 222. Next, the SMF 220 sends a SessionUpdate Request message (4718) to the UPF 212. Next, the SMF 220 receivesa Session Update Response message (4720) from the UPF 212. Other stepsmay be added to the method (4900).

FIG. 50 illustrates, in a message flow diagram, an example of a servicerequest procedure (5000), in accordance with an embodiment of thepresent invention. The UE 202 may send to the (R)AN 204 a MM NAS servicerequest (5002). The message (5002) may include PDU session ID(s),security parameters, and PDU session status. The UE 202 may send NASmessage service request towards the AMF 218 encapsulated in an RRCmessage to the RAN 204.

If the UE 202 is in the CM-IDLE state, then the UE 202 may send the MMNAS service request message (5002). The UE 202 may include the 5Gtemporary ID into the RRC message (5002) between the UE 202 and the(R)AN 204. The (R)AN 204 may route the MM NAS service request message tothe correct AMF 218 according to the 5G temporary ID. If the UE 204 isin the CM-IDLE state, then the UE 202 may send the MM NAS servicerequest (5002) message. The UE 202 may include security parameters inthe NAS message (5002). The PDU session status may be included.Alternatively, the PDU session status may be included only if the UE 202has released some PDU sessions but has not informed the SMF 220.

If the UE 202 is in the CM-CONNECTED state, the UE 202 may send the MMNAS service request (5002) message. The MM NAS service request message(5002) may be encrypted and integrity protected. The message (5002) mayinclude PDU session ID(s) to be activated. The PDU session status may beincluded. Alternatively, the PDU session status may be included if theUE 202 has released some PDU sessions but has not informed the SMF 220.

If the UE 202 is triggered for user data, the UE 202 may include the PDUsession ID(s) in the NAS service request message (5002) to indicate thePDU session that the UE 202 selects to activate. If the UE 202 istriggered for signalling only, the UE 202 may not send any PDU sessionID. When this procedure (5000) is triggered for paging response, if theUE 202 needs to activate the PDU session(s), it includes the PDU sessionID(s) in the MM NAS service request (5002) message to indicate the PDUsession that the UE 202 needs to activate. Otherwise the UE 202 does notneed to include any PDU session ID. The PDU session status may indicatethe PDU sessions available in the UE 202.

Next, the (R)AN 204 may send to the AMF 218 a N2 Message (MM NAS servicerequest (5004). The message (5004) may include a 5G temporary ID,location information, a RAT type, and a RRC establishment cause. If theAMF 218 cannot handle the service request (5004) it will reject it.

If the UE 202 is in the CM-IDLE state, then the 5G temporary ID may beobtained in a RRC procedure. The RAN 204 may select the AMF 218according to the temporary ID. The location information and the RAT typerelate to the cell in which the UE 202 is camping.

If the UE is in CM-CONNECTED state, the (R)AN 204 forwards the MM NASService Request message to the AMF 218 without adding the 5G temporaryID, location information, RAT type, or RRC establishment cause.

Based on the PDU session status, the AMF 218 may initiate a PDU sessionrelease procedure if the PDU session is not available in the UE 202.

Next, if the service request (5004) was not sent integrity protected, orintegrity protection is indicated as failed, the AMF 218 may initiateNAS authentication/security procedure (5006) with the UE 202 and theAUSF 214. If the UE 202 is triggered to establish signalling connection,after the security exchange the UE 202 can send uplink signalling andthe rest of this procedure are skipped. If the UE is in CM-CONNECTEDstate, step (5006) is skipped.

Next, the AMF 218 may conditionally send to the SMF 220 a N11 message(5008) that includes an UE identifier (SUPI) and PDU session ID(s). Ifthe MM NAS service request (5004) message includes PDU session ID(s), orthis procedure is triggered by SMF 220, the AMF 218 may send a N11message (5008) to the SMF(s) 220 associated with the PDU session ID(s).Next, the SMF 220 may conditionally send to the AMF 218 a N11 message(5010) that includes N2 SM information (QoS profile, CN N3 tunnelinformation) and SM NAS Session Activation Accept (with PDU session IDs)to the AMF 218. After receiving the N11 message (5008), each SMF 220 maysend a N11 message (5010) to the AMF 218 to establish the user plane(s)for the PDU sessions. The N2 SM Information may include information thatthe AMF 218 may provide to the RAN 204. The SM NAS Session ActivationAccept message may include information that the AMF 218 may provide tothe UE 202. The SMF 220 may use a “Message Transfer” service provided bythe AMF 218 to send N2 SM information and SM NAS Session ActivationAccept.

Next, the AMF 218 may conditional send to the (R)AN 204 a N2 request(5012) that includes N2 SM information and SM NAS session activationaccept received from the SMF 220, a security context, an AMF 218signalling connection ID, a handover restriction list, and a MM NASservice accept. If the service request (5000) was triggered by a UE 202in the CM-IDLE state, the AMF 218 may include the security context, anAMF signalling connection ID, and a handover restriction list in the N2request (5012). The RAN 204 may store the security context, AMFsignalling connection ID, QoS information for the QoS flows of the PDUsessions that are activated and N3 tunnel IDs in the UE RAN context. Ifthe service request (5000) was triggered when the UE 202 is in theCM-CONNECTED state, the AMF 218 may transfer the N2 SM Information (QoSprofile, CN N3 tunnel information) and SM NAS Session Activation Acceptto the (R)AN 204, without adding the security context, the AMFsignalling connection ID, the handover restriction list, or the MM NASservice accept. If there are multiple PDU sessions that involve multipleSMFs 220, the AMF 218 may wait for responses from all SMFs 220 in step(5010) until it sends the N2 request (5012) to the RAN 204. The MM NASservice accept may include PDU session status in the AMF 218. If thisprocedure (5000) is triggered for signalling only, the MM NAS serviceaccept can be sent to the UE 202 after step (5006).

Next, the (R)AN 204 and the UE 202 may perform a RRC connectionreconfiguration (600B) depending on the QoS information for all the QoSflows of the PDU sessions activated. If the service request procedure(5000) was triggered by a UE 202 in the CM-IDLE state, the user planesecurity may be established at this step (600A). The RAN 204 may forwardthe MM NAS service accept and SM NAS Session Activation Accept to the UE202. If the service request procedure (5000) was triggered by a UE inthe CM-IDLE state, the UE 202 may remove the context of PDU sessionsthat are not available in the 5G CN.

After the user plane radio resources are setup, the uplink data from theUE may be forwarded (5014) to the RAN 204. The 5G RAN 204 may send theuplink data (5014) to the UPF 212 address and tunnel ID provided in thestep (5008). Next, the (R)AN 204 may conditionally send to the AMF 218 aN2 request ACK (5016) that includes N2 SM information (RAN tunnelinformation, a list of accepted QoS flows for each of the PDU sessionsactivated, and a list of rejected QoS flows for each of the PDU sessionsactivated.

Next, the AMF 218 may conditionally send to the SMF 220 a N11 message(5018) that includes N2 SM information (RAN tunnel information), a RATtype, a list of accepted QoS flows, and a list of rejected QoS flows peraccepted PDU session to the SMF 220. If the UE 202 time zone has changedcompared to the last reported UE time zone, then the AMF 218 may includethe UE time zone IE in this message (5018). For rejected QoS flows, theSMF 220 may send an SM NAS release QoS flows request to the UE 202. Themessage (5018) may include PDU session ID(s) and a list of rejected QoSflow for each PDU session. The UE 202 then may confirm the release ofrejected QoS flows. Optionally, if dynamic PCC is deployed, SMF 220 mayinitiate an IP-CAN session modification (4716) and provide new locationinformation to the PCF 222.

Next, the SMF 220 may conditionally send to the UPF 212 a N4 sessionupdate request (4718) that includes RAN tunnel information and a list ofaccepted QoS flows. If a user plane is to be setup or modified, the SMF220 may initiate a N4 session modification procedure and provide RANtunnel information. The UPF 212 may then conditionally send to the SMF220 a N4 session update response (4720). Next, the SMF 220 mayconditionally send to the AMF 218 a N11 message ACK (e).

When the network needs to signal (e.g., N1 signalling to a UE 202,Mobile-terminated SMS, PDU session radio resource establishment todeliver mobile terminating user data data) with a UE 202 in a 5G CM-IDLEstate or a 5G CM-CONNECTED state, the network may initiate a networktriggered service request procedure. If the UE 202 is in the 5G CM-IDLEstate, the network triggered service request procedure may send a pagingrequest to the (R)AN 204/UE 202. The paging request triggers the servicerequest procedure in the UE 202. If the UE 202 is in the 5G CM-CONNECTEDmode, no paging request will be sent to the (R)AN 204/UE 202.

FIG. 51 illustrates, in a message flow diagram, an example of a servicerequest procedure (5100), in accordance with an embodiment of thepresent invention. When UPF 212 receives downlink data on a PDU sessionand there is no AN 204 tunnel information stored in UPF 212 for the PDUsession, the UPF 212 may buffer the downlink data (e). The UPF 212 maythen send to the SMF 220 a data notification (5104) that includes thePDU session ID, and priority. On arrival of the first downlink datapacket, the UPF 212 may send the data notification (5104) message to theSMF 220. If the UPF 212 receives additional downlink data packets for aQoS flow in the same PDU session with the same or lower priority thanthe first data notification (5104) was sent for, the UPF 212 may bufferthese downlink data packets and does not send a new data notification.If a paging policy differentiation feature is supported by the UPF 212and if it is activated by the SMF 220 for this N4 session, the UPF 212may also include the DSCP in TOS (IPv4)/TC (IPv6) value from the IPheader of the downlink data packet. The SMF 220 may send to the UPF 212a data notification acknowledgement (ACK) (5106).

Next, the SMF 220 may send a N11 message (5108) to the AMF 218,including a UE permanent ID, a PDU session ID, and a priority. The SMF220 identifies the AMF 218 and sends it a N11 message (5108) includingthe UE permanent ID, the PDU session ID, the priority, and a pagingpolicy indication. The priority and PDU session ID may be set accordingto step (5104). If the SMF 220, while waiting for the user plane to beestablished, receives an additional data notification message (5104)with higher priority than the first N11 message (5108) was sent for, theSMF 220 may send a new N11 message (5108) indicating the higher priorityand PDU session ID to the AMF 218. If the SMF 220, while waiting for theuser plane to be established, receives a N11 message from an AMF 218other than the one it sent a N11 message (5108) to, the SMF 220 mayre-send the N11 message (5108) only to the new AMF 218 from which itreceived the N11 message. If the registration procedure with the AMF 218change is in progress when the old AMF 218 receives the N11 message(5108), the old AMF 218 may reject the N11 message with an indicationthat the N11 message has been temporarily rejected. When supportingpaging policy differentiation, the SMF 220 may indicate in the N11message (5108) that the paging policy indication related to the downlinkdata that triggered the data notification message. It is noted that theAMF 218 may receive request message(s) from other network functionswhich leads to signalling towards UE 202/RAN 204, e.g., networkinitiated detach, and SMF 220 initiated PDU session modification. If theUE 202 is in the 5G CM-CONNECTED state and the AMF 218 only delivers N1message towards UE 202, the flow continues in step (5116) below.

The AMF 218 may respond to the SMF 220. If the UE 202 is in the 5GCM-IDLE state, and the AMF 218 considers that the UE 202 is notreachable for paging, the AMF 218 may send a response (5110) to the SMF220, with cause code and information. The SMF 220 may deliver thisfurther information to the UPF 212. If the UE 202 is in the 5GCM-CONNECTED state, the AMF 218 may send a response (5110) to the SMF220 with an indication that the UE 202 is in the 5G CM-CONNECTED modeand then the SMF 220 may perform step (5010) to (5020) in the UEtriggered service request procedure (5000) to establish the radioresources and N3 tunnel of the PDU session. The rest of this procedureis omitted.

If the UE 202 is registered in the AMF 218 and is in the 5G CM-IDLE butconsidered reachable for paging, the AMF 218 may send a paging message(5112) including a NAS ID for paging, a registration area, a paging DRXlength, and a paging priority indication, to each (R)AN 204 nodebelonging to the registration area(s) in which the UE 202 is registered.When supporting paging policy differentiation, the AMF 218 may includepaging policy indication in the paging request message (5112). Pagingstrategies may be configured in the AMF 218 for different combinationsof DNN, paging policy indication, PDU session IDs from SMF 220 whenavailable (see clause 4.9) and other PDU session context informationidentified by the PDU session ID received in the N11 message. Pagingstrategies may include a paging retransmission scheme (e.g., howfrequently the paging is repeated or with what time interval);determining whether to send the paging message to the (R)AN 204 nodesduring certain AMF 218 high load conditions; whether to apply sub-areabased paging (e.g., first page in the last known cell-id or TA andretransmission in all registered TAs). The AMF 218 and the (R)AN 204 maysupport further paging optimisations in order to reduce the signallingload and the network resources used to successfully page a UE 202 by oneor several following means: by the AMF 218 implementing specific pagingstrategies (e.g., the N2 paging message is sent to the (R)AN 204 nodesthat served the UE 202 last); by the AMF 218 considering information onrecommended cells and RAN nodes provided by the (R)AN 204 at transitionto CN-IDLE. The AMF 218 may take the (R)AN 204 nodes related part ofthis information into account to determine the (R)AN 204 nodes to bepaged, and may provide the information on recommended cells within theN2 paging message to each of these (R)AN 204 nodes; and by the (R)AN 204considering the paging attempt count information provided by the AMF 218at paging. If the UE radio capability for paging information isavailable in the AMF 218, the AMF 218 adds the UE radio capability forpaging information in the N2 paging message (e) to the (R)AN 204 nodes.If the information on recommended cells and (R)AN 204 nodes for pagingis available in the AMF 218, the AMF 218 may take that information intoaccount to determine the (R)AN 204 nodes for paging and, when paging a(R)AN 204 node, the AMF 218 may transparently convey the information onrecommended cells to the (R)AN 204 node. The AMF 218 may include in theN2 paging message(s) (5112) the paging attempt count information. Thepaging attempt count information may be the same for all (R)AN 204 nodesselected by the AMF 218 for paging.

Next, the (R)AN 204 node may conditionally page (5114) the UE 202. Ifthe (R)AN 204 nodes receive paging messages (5112) from the AMF 218, theUE 202 is paged (5224) by the (R)AN 204 node. When the UE 202 is in the5G CM-IDLE state, upon reception of a paging request, the UE 202 mayinitiate the UE triggered service request procedure (5000). In step(5008), the AMF 218 may send a N11 message to both SMF(s) 220 associatedwith the PDU session identified by PDU session ID(s) in MM NAS servicerequest message, and to SMF(s) 220 from which it receives the N11message in step (5006). The AMF 218 supervises the paging procedure witha timer. If the AMF 218 receives no response from the UE 202 to thepaging request (5224) message, it may repeat the paging according to anyapplicable paging strategy described in step (5108). If the AMF 218receives no response from the UE 202 after this paging repetitionprocedure, the AMF 218 may use the N11 message to notify the SMF 220about the paging failure, if paging was triggered by a N11 message,unless the AMF 218 is aware of an ongoing MM procedure that prevents theUE 202 from responding (i.e., the AMF 218 receives a context requestmessage indicating that the UE 202 performs TAU procedure with anotherAMF 218. When a downlink data notification reject message is received,SMF 220 informs the UPF 212, and the UPF 212 deletes the bufferedpacket(s). Next, the UPF 212 transmits the buffered downlink data (5116)toward the UE 202 via the (R)AN 204 node which performed the servicerequest procedure. The network may send downlink signalling (5116) ifthe procedure is triggered due to a request from other network entitiesdescribed in step (5108).

FIG. 52A illustrates, in a state diagram, an example of a sessionmanagement state model 5200A in a UE 202, in accordance with anembodiment of the present invention. The session state may transitionfrom a Session-IDLE state 610A to a Session-ACTIVE state 620A when aservice request is accepted from the AMF 218. The session state of theUE 202 may transition from the Session-ACTIVE state 620A to theSession-IDLE state 610A when the RRC is released.

FIG. 52A further illustrates, in a state diagram, an example of asession management state model 5200A in a UE 202, in accordance withembodiments of the present invention. When a new PDU session request isaccepted, the PDU Session State is created as part of UE's PDU sessioncontext, and the PDU Session State is set to the Session-ACTIVE state620A. When the RRC is released, the PDU Session State is set to theSession-IDLE state 610A. When the UE 202 sends a service request totransmit uplink data or to receive downlink data, and the UE 204receives a Service Request Accept message from the AMF 218, and the PDUSession State is set to the Session-ACTIVE state 620A.

FIG. 52B illustrates, in a state diagram, an example of a sessionmanagement state model 5200B in an AMF 218 and/or a SMF 220, inaccordance with an embodiment of the present invention. The sessionstate may transition from a Session-IDLE state 610B to a session-ACTIVEstate 620B after session activation completion. The session state maytransition from the Session-ACTIVE state 620B to the Session-IDLE state610B when the N2 connection is released.

The session state may be used to indicate that the UE 202 has activateda PDU session to send and receive data. Two session states include theSession-ACTIVE state and the Session-IDLE state. The UE 202, the servingAMF 218, and the serving SMF 220 maintain the session state.

When a PDU session is in the Session-IDLE state, the UP data connectionbetween the UE 202 and the UPF 212 terminating N3 connection is notestablished. The UE 202 may not send or receive data. The (R)AN 204 maynot have PDU session context. The UPF 212 terminating N3 connection mayhave the UE's PDU session context, but without (R)AN 204 N3 connectioninformation (i.e., no address of (R)AN 204 and N3 tunnel endpointidentifier). The SMF 220 may keep the UE's PDU session contextinformation relevant to the SMF 220, but without (R)AN 204 information.The AMF 218 may keep all UE's PDU session context information relevantto the AMF 218.

When a PDU session is in Session-ACTIVE state, the UE 202 may send andreceive data. The Uu air interface between the UE 202 and (R)AN 204 maybe established. The N3 connection may be established when the PDUsession is activated. The UE 202 may have all PDU session contextinformation, including DRB information. The AMF 218 may keep all UE'sPDU session context information relevant to the AMF 218. The SMF 220 maykeep all of the UE's PDU session context information relevant to the SMF220. The (R)AN 204 may monitor the data activity of PDU sessions. Aninformation element “Time of Last Data Activity” in the PDU sessioncontext at the (R)AN 204 may be used to record the last time the UE 202had data activity. During a handover procedure, this information elementmay be transferred to the target (R)AN 204 t and unmodified as part ofthe UE context. Each PDU session context may also have a SessionInactive Timer. During the handover procedure, the (R)AN 204 N3connection information at the UPF 212 terminating N3 connection may beupdated if the PDU session has data activity.

Another parameter, “N3 Status Flag”, in UE's PDU session context at the(R)AN 204 may be used to indicate whether the (R)AN 204 information inthe UPF 212 is updated or not. The N3 Status Flag in the (R)AN 204 mayhave two values: N3_AT_UPF_UPDATED and N3_NOT_AT_UPF_UPDATED. During thehandover procedure, the target (R)AN 204 t compares the duration thatthe UE 202 has no data activity (from the current time and Time of LastData Activity parameter) and the Session Inactive Timer parameter. Ifthe duration that the UE 202 has no data activity is longer, the target(R)AN 204 t may conclude that the UE 202 has no data activity.Otherwise, the target (R)AN 204 t may conclude that the UE 202 has dataactivity. The (R)AN N3 tunnel information at the UPF terminating N3connection is updated only if the PDU session has data activity. Whenthe PDU session information is sent to the (R)AN 204 during a sessionestablishment procedure and a session request procedure, the N3 StatusFlag in the (R)AN 204 may be set to N3_AT_UPF_UPDATED. The N3 StatusFlag in the (R)AN 204 may be changed from N3_AT_UPF_UPDATED toN3_AT_UPF_NOT_UPDATED during the handover procedure, by the target (R)AN204 t if the PDU session has no data activity in a source (R)AN 204 s.The N3 Status Flag in the (R)AN 204 may be changed fromN3_AT_UPF_NOT_UPDATED to N3_AT_UPF_UPDATED if the PDU session has dataactivities.

During a handover process, the target (R)AN 204 t may send to the AMF218 a list of PDU sessions that are considered as having no dataactivity marked by the target (R)AN 204 t in the path switch request.The target (R)AN 204 t may include another list of the PDU sessions thathave N3 Status Flag as N3_AT_UPF_NOT_UPDATED already set by the source(R)AN 204 s. For each PDU session, the target RAN 204 t may include the(R)AN 204 information of the PDU sessions, such as (R)AN type, (R)AN N3address and (R)AN N3 tunnel endpoint identifier, and a list of acceptedQoS flows and another list of QoS rejected flows. The AMF 218 may storethe (R)AN information. The AMF 218 may inform the corresponding servingSMF 220 of the PDU session ID(s) that have no data activity marked bythe target (R)AN 204 t in the path switch request. The SMF 220 may senda message to the serving UPF 212 to release the (R)AN N3 tunnelinformation.

The AMF 218 and the SMF 220 may have a N3 Status Flag as part of theirUE's PDU session context. When the PDU session is established oractivated, the N3 Status Flag in the AMF 218 and SMF 220 may be set toN3_AT_UPF_UPDATED. The N3 Status Flag in AMF 218 and SMF 220 may bechanged from N3_AT_UPF_UPDATED to N3_AT_UPF_NOT_UPDATED when receivingthe message from the (R)AN 204 indicating that this PDU Session has nodata activity. The N3 Status Flag in AMF 218 and SMF 220 may be changedfrom N3_AT_UPF_NOT_UPDATED to N3_AT_UPF_UPDATED when the UE 202 has dataactivity notified by the UPF 212 or the (R)AN 204.

Table 2 states the description of the session states session-ACTIVE andsession-IDLE for various network entities.

TABLE 2 Description of Session State Network Entity Session-ACTIVESession-IDLE UE (maintains Has all PDU session context, Has PDU sessioncontext Session State) including DRB information without DRB information(R)AN (does not Has all PDU session context Has no PDU session (maintainSession and DRB information context and no DRB State) information UPF(does not Has all PDU session context Has PDU session context (maintainSession information without (R)AN N3 State) connection information AMF(maintains Has all PDU session context Has all PDU session contextSession State) information relevant to access and information relevantto access mobility management. and mobility management. SMF (maintainsHas all PDU session context Has PDU session context Session State)information. However, depending without (R)AN information, on N3 StatusFlag, the SMF may such as (R)AN type and not have (R)AN information,such (R)AN N3 connection as (R)AN type and (R)AN N3 information.connection information, if on N3 Status Flag is N3_AT_UPF_NOT_UPDATED.

FIG. 52B further illustrates, in a state diagram, an example of asession management state model 5200B in an AMF 218 and/or a SMF 220, inaccordance with embodiments of the present invention. When a new PDUsession request is accepted, the PDU Session State is created as part ofUE's PDU session context in the AMF 218 and in the SMF 220, and the PDUSession State is set to the Session-ACTIVE state 620A. When the N2 isreleased, the PDU Session State of all PDU sessions in the AMF 218 andthe SMF 220 transition from the Session-ACTIVE state 620A to theSession-IDLE state 610A. When the UE 202 Service Request including thePDU Session Activation request is accepted, the PDU Session State ofrequested PDU Session transitions from the Session-IDLE state 610A tothe Session-ACTIVE state 620A.

In the 3GPP TS 23.502, clause 4.2.3.2 on UE triggered Service Request inCM-IDLE state, a UE triggered Service Request in the CM-IDLE stateprocedure is described. Step 5 of that procedure pertains to the AMF 218sending a N2 Request message to the (R)AN 204. It is noted that thismessage may include a Monitor Data Activity Flag in addition to a N2 SMinformation received from SMF 220, a security context, an AMF SignallingConnection ID, a Handover Restriction List, and a MM NAS Service Accept.The (R)AN 204 stores the Security Context, AMF Signalling Connection Id,QoS Information for the QoS Flows of the PDU Sessions that areactivated, N3 Tunnel IDs, and the Monitor Data Activity Flag in the UERAN context.

An Xn based inter NG (R)AN handover may take place with and without UPF212 relocation. The handover may be based on a centralized deployment oron a local deployment. Separate call flows may be defined for roamingscenarios.

The AMF 218 analyzes the mobility pattern of the UE 202 and determines,based on the mobility pattern, whether to request the (R)AN 204 tomonitor data activity of individual PDU sessions. If the AMF 218requests the (R)AN 204 to monitor data activity of individual PDUsessions, then after the PDU session is established or activated, the(R)AN 204 records the last time a PDU session has data activity via aparameter, such as a parameter named “Time of Last Data Activity”.During the handover procedure, the Time of Last Data Activity parameteris transferred to the target (R)AN 204 t and unmodified as part of theUE's PDU context. The target (R)AN 204 t sends the Time of Last DataActivity parameter of PDU sessions in the list of PDU sessions thatrequire a path switch in the Path Switch request.

Alternatively, the AMF 218 may inform the SMF 220 about the UE 202mobility pattern during a Session Establishment procedure. The SMF 220may then determine whether to monitor the data activity of individualPDU sessions. In this case, during the Session Establishment procedure,the SMF 220 requests the (R)AN 204 to monitor data activity of PDUsession.

For each PDU session included in the path switch request, the SMF 220decides whether or not to update the (R)AN tunnel information for theUPF 212 based on criteria. The criteria may include at least one of: themobility patter of the UE 202, a PDU session type, the length of timethat the UE 202 has no data activity, and whether there are other PDUsession served by the same UPF 212. With the mobility pattern of the UE202, only the UE 202 requesting handover is considered. The PDU sessiontype may be stored as a part of the Attributes of a PDU session. Howlong the UE has no data activity is based on the Time of Last DataActivity reported by (R)AN 204 as instructed by the AMF 218.

The AMF 218 and the SMF 220 each have a parameter, named “N3 Connectionstatus”, as part of their UE's PDU session context. The N3 ConnectionStatus has two values: N3 CONNECTED and N3 DISCONNECTED. When the PDUsession is established or activated, the N3 Connection Status in the AMF218 and the SMF 220 are set to N3_CONNECTED. The N3 Connection Status ofa PDU session in the AMF 218 is changed from N3_CONNECTED toN3_DISCONNECTED when the AMF 218 receives a message from the SMF 220indicating that the (R)AN information is not updated for this PDUSession during handover procedure. The N3 Connection Status of a PDUsession in the SMF 220 is changed from N3_CONNECTED to N3_DISCONNECTEDwhen the SMF 220 decides not to update the UPF 212 with (R)ANinformation during handover procedure. The N3 Connection Status in AMF218 and SMF 220 is changed from N3_DISCONNECTED to N3_CONNECTED when theUE 202 has data activity notified by the UPF 212 or the (R)AN 204.

During the handover process, the target (R)AN 204 t sends to the AMF 218the list of PDU sessions to be switched and to be released in the pathswitch request. The PDU sessions to be switched are the PDU sessionsthat have UPF N3 tunnel information. For each PDU session to beswitched, the target RAN 204 t includes the Time of Last Data Activityparameter, and the target (R)AN information, such as the (R)AN type, the(R)AN address and the (R)AN N3 Tunnel Endpoint Identifier. The AMF 218stores the (R)AN type. The AMF 218 informs the corresponding serving SMF220 of the PDU Session ID(s) to be switched and to be released. For PDUsessions to be switched, the SMF 220 determines whether or not to updatethe (R)AN information for the UPF 212. If the SMF 220 determines toupdate (R)AN information for the UPF 212, the SMF 220 sends (R)AN N3tunnel information to the UPF 212. If the SMF 220 determines not toupdate the (R)AN information, the SMF 220 sends a request message to theUPF 212 to delete the (R)AN N3 tunnel information. The SMF 220 informsthe AMF 218 of its determination of whether or not to update the (R)ANinformation at the UPF 212. For the PDU sessions where the (R)ANinformation is updated in the UPF 212, the N3 Connection Status in theAMF 218 and the SMF 220 is set to N3 CONNECTED. Otherwise, the N3Connection Status in the AMF 218 and the SMF 220 is set toN3_DISCONNECTED. During the N2 Release procedure, the AMF 218 sends a N2Release Notification message to the SMF(s) 220 that serves PDU sessionsthat are in the Session-ACTIVE state and have the N3 Connection Statusset to N3 CONNECTED.

FIG. 53 illustrates, in a message flow diagram, an example of a Xn basedinter NG RAN handover procedure (5300) without UPF 212 relocation, inaccordance with an embodiment of the present invention. This procedure(5300) may be used to hand over a UE 202 from a source RAN 204 to targetRAN 204 t using Xn when the AMF 218 is unchanged and the SMF 220 decidesto keep the existing UPF 212 (i.e., the UPF 212 which terminates the N3interface in the NG Core Network (NGC). The presence of IP connectivitybetween the source UPF 212 and target UPF 212 is assumed.

The procedure (5300) includes handover preparation (5302) and handoverexecution (5304). The handover execution (5304) includes the forwardingof data (5306) from a source RAN 204 s to a target RAN 204 t. The targetRAN 204 t may check whether some PDU sessions having a N3 Status Flag“N3_AT_UPF_UPDATED” but having no data activity in the source RAN 204 sby reading the parameter “Time of Last Data Activity” in the PDU sessioncontext. If the duration that a PDU has no data activity is longer thanthe parameter Session Inactive Timer, the PDU session is considered ashaving no data activity. The target RAN 204 t may send an N2 path switchrequest message (5308) to an AMF 218 to inform that the UE 202 has movedto a new target cell, and a list of PDU sessions to be switched orremoved, a list of PDU sessions that have no data activity marked by thetarget RAN 204 t and a list of PDU sessions that have no data activitymarked by the source RAN 204 s. Depending on the type of target cell,the target RAN 204 t may include appropriate information in this message(5308) for each PDU session, including RAN type, N3 RAN Address and N3tunnel endpoint identifier. If the target RAN 204 t cannot support someQoS flows of a PDU session, the N2 path switch request message (5308)may include the list of accepted QoS flows and the list of rejected QoSflows for this PDU session.

Next, the AMF 218 may send a N11 message (5310) to each SMF 220associated with the lists of PDU sessions received in the N2 path switchrequest (5308). For the PDU sessions that require a path to be switched,upon receipt of the N11 message (5310), each of these SMFs 220determines whether the existing UPF 212 can continue to serve the UE202. If the existing UPF 212 cannot continue to serve the UE 202 and itis not a PDU session anchor, steps (5608) to (5624) of FIG. 56, asdescribed below, are performed. Otherwise, the following steps (5312) to(5318) are performed by each of these SMFs 220 if their existing UPFs212 can continue to serve the UE 202. For the PDU sessions that are inthe list of PDU sessions having no data activity marked by the sourceRAN 204 s and the list of PDU sessions having no data activity marked bytarget RAN 204 t, the AMF 218 may store the RAN 204 information. Foreach PDU session in the list of PDU sessions having no data activitymarked by the target RAN 204 t, the AMF 218 may send the N11 message(5310) to the SMF 220 to forward the PDU Session ID to notify that thePDU session has no data activity.

Next, the SMF 220 may initiate a release of PDU sessions which are notrequested by the target RAN 204 t. For PDU sessions requested by thetarget RAN 204 t, the SMF 220 may send an N4 session modificationrequest (including RAN address, tunnel identifiers for downlink userplane, list of accepted flows if present) message (5312) to the UPF 212.For the PDU sessions where the RAN 204 information is to be released,the SMF 220 may send an N4 session modification request (5312) to theUPF 212 for these PDU sessions. The message (5312) may indicate therelease of RAN N3 connection information (i.e., RAN address and tunnelidentifier for the downlink user plane). Next, the UPF 212 returns an N4session modification response (including tunnel identifiers for uplinktraffic) message (5314) to the SMF 220 after the requested PDU sessionsare switched or modified. In order to assist the reordering function inthe target RAN 204 t for PDU sessions requiring a path switched, the UPF212 may send one or more “end marker” packets (5316) on the old pathimmediately after switching the path. The UPF 212 may start sendingdownlink packets (5318) to the target RAN 204 t. It is noted that step(5318) can occur any time after receipt of the N4 session modificationresponse (5314) at the SMF 2200. In the SMF 220, for PDU sessions havingno data activity, the parameter N3 Status Flag of these PDU sessions maybe changed from N3_AT_UPF_UPDATED to N3_AT_UPF_NOT_UPDATED. The SMF 220may send an N11 message acknowledgement (ACK) (5320) (including CNtunnel information) to the AMF 212 for PDU sessions which have beenswitched or modified successfully.

After receiving the N11 message response (5320) from the SMFs 220, forPDU sessions having no data activity marked by the target RAN 204 t, theAMF 218 may change the parameter N3 Status Flag of these PDU sessionsfrom N3_AT_UPF_UPDATED to N3_AT_UPF_NOT_UPDATED. Once the N11 messageresponse (5320) is received from all the SMFs 220, the AMF 218 mayaggregate the received CN tunnel information from these responses andsend this aggregated information as a part of N2 SM information in a N2path switch request ACK (5322) to the target RAN 204 t. If none of therequested PDP sessions have been switched successfully, the AMF 218 maysend an N2 path switch request failure message to the target RAN 204 t.In the target RAN 204 t, for PDU sessions having no data activity markedby the target RAN 204 t, the parameter N3 Status Flag of these PDUsessions may be changed from N3_AT_UPF_UPDATED to N3_AT_UPF_NOT_UPDATED.By sending a release resources message (5324) to the source RAN 204 s,the target RAN 204 t confirms success of the handover. It then triggersthe release of resources with the source RAN 204 s.

FIG. 53 further illustrates, in a message flow diagram, an example of aXn based inter NG (R)AN handover procedure (5300) without user planefunction relocation and with session deactivation, in accordance withembodiments of the present invention. The procedure (5300) provides analternative solution that combines the handover procedure defined inclause 4.9.1.1 of TS 23.502 and the session deactivation signallingmessages.

This procedure (5300) is used in a handover of a UE 202 from a sourceRAN 204 s to target RAN 204 t using Xn when the AMF 218 is unchanged andthe SMF 220 determines to keep the existing UPF 212. The UPF 212 is theUPF which terminates the N3 interface in the NGC. The presence of IPconnectivity between the source UPF 212 s and the target UPF 212 t isassumed. When the PDU is established, the SMF 220 sends to the (R)AN 204a timer parameter, for example, named “Session_Inactivity_Timer”. Thesource (R)AN 204 s records the last time the PDU session has dataactivity using the “Time of Last Data Activity” parameter. The source(R)AN 204 s sends the Session_Inactivity_Timer parameter and the Time ofLast Data Activity parameter to the target (R)AN 204 t as part of UE'sPDU session context. If a PDU session does not have data activity for aperiod longer than the Session_Inactivity_Timer parameter, the target(R)AN 204 t determines to initiate the PDU session deactivationprocedure.

In the Handover Execution step, the target (R)AN 204 t sends the UE 202an RRC signalling message that indicates if the PDU sessions that areaccepted, deactivated, or rejected. Then the target (R)AN 204 t informsthe SMF 220 (via the AMF 218) that the PDU sessions that are accepted,deactivated, or rejected. For PDU sessions that are accepted, the target(R)AN 204 t includes the (R)AN N3 tunnel information, such as the (R)ANAddress and the Tunnel Endpoint Identifier. For PDU sessions that areaccepted, the SMF 220 requests the UPF 212 to update the (R)AN tunnelinformation. For PDU sessions that are deactivated, the SMF 220 sends amessage requesting the UPF 212 to delete the (R)AN tunnel information.For PDU sessions that are released, the SMF 220 initiates the PDUSession Release procedure.

The target RAN 204 t sends a N2 Path Switch Request (5308) message to anAMF 218 that indicates that the UE 202 has moved to a new target cell.The message (5308) includes a list of PDU Sessions to be switched,deactivated, or removed. Depending on the type of target cell, thetarget RAN 204 t includes other information in this message. The PDUsessions to be switched are the PDU sessions having UPF N3 tunnelinformation. For each PDU session to be switched, the target (R)AN 204 tincludes the Time of Last Data Activity parameter, and the (R)ANinformation (such as the N3 (R)AN Address and the N3 tunnel endpointidentifier). If the target RAN 204 t cannot support a QoS flow of a PDUsession, the N2 Path Switch Request (5308) message includes the list ofaccepted QoS flows and the list of rejected QoS flows for this PDUsession.

The AMF sends a N11 Message (5310) to each SMF 220 associated with thelist of PDU Sessions received in the N2 Path Switch Request (5308)message. For the PDU sessions that require a path switch, upon receiptof the N11 Message (5310), each of these SMFs 220 determines whether ornot the existing UPF 212 can continue to serve the UE 202. If theexisting UPF 212 cannot continue to serve the UE 202, and it is not aPDU session anchor, steps 3-11 of clause 4.9.1.2 of TS 23.502 areperformed. For each PDU session where a path switch is required, the SMF220 determines whether or not the existing UPF 212 needs to be updatedwith the (R)AN 204 tunnel information, according to clause 5.6.X of TS23.501.

The SMF 220 initiates release of PDU Sessions which are not requested bythe target RAN 204 t. For PDU sessions requested by the target RAN 204t, the SMF 220 sends a N4 Session Modification Request (6408) message tothe UPF 212. The message (5312) includes the (R)AN address, the tunnelidentifiers for the downlink user plane, and the list of accepted flows,if present. For the PDU sessions to be deactivated, the (R)ANinformation does not need to be updated. The SMF 220 sends a N4 SessionModification Request (5312) message to the UPF 212 for those PDUsessions. The message (5312) indicates the release of the (R)AN N3tunnel information, such as the (R)AN Address and the Tunnel EndpointIdentifier for the downlink user plane. The UPF 212 returns a N4 SessionModification Response (5314) message to the SMF 220 after the requestedPDU Sessions are switched or modified. The message (5314) includes theTunnel identifiers for uplink traffic.

In order to assist the reordering function in the target RAN 204 t forPDU sessions requiring a path switch, the UPF 212 sends one or more “endmarker” packets (5316) on the old path immediately after switching thepath. The UPF 212 starts sending downlink packets to the target RAN 204t. The SMF 220 sends a N11 Message ACK (5318) message to the AMF 218 forthe PDU sessions which have been successfully switched or deactivated.The message (5318) includes the CN Tunnel Information and indicateswhether the (R)AN N3 tunnel information is updated (e.g., path switched)or deleted (e.g., PDU sessions deactivated). In the SMF 220, for PDUsessions where the N3 (R)AN tunnel information is deleted from the UPF212, the session state is set to Session-IDLE. It is noted that step(5318) can occur any time after receipt of N4 Session ModificationResponse (5314) message at the SMF 220.

In the AMF 218, upon receiving the N11 Message ACK (5318) message, theSession State of the deactivated PDU sessions is set to Session-IDLE.Once the N11 Message Response (5318) is received from all the SMFs 220,the AMF 218 aggregates received CN Tunnel Information from theseresponses and sends this aggregated information as a part of N2 SMInformation in a N2 Path Switch Request ACK (5320) message to the targetRAN 204 t. The message (5320) includes an indication, for each PDUsession, whether or not the UPF 212 is updated with (R)AN information.If none of the requested PDP Sessions have been successfully switched,the AMF 218 sends an N2 Path Switch Request Failure message to thetarget RAN 204 t. In the target RAN 204 t, for PDU sessions where theUPF 212 is not updated with the (R)AN information, the UPF N3 tunnelinformation is deleted. By sending a Release Resources (5322) message tothe source RAN 204 s, the target RAN 204 t indicates success of thehandover. It then triggers the release of resources with the source RAN204 s.

FIG. 53 further illustrates, in a message flow diagram, an example of aXn based inter NG (R)AN handover procedure (5300) without UPF 212relocation, in accordance with an embodiment of the present invention.This procedure (5300) may be used to hand over a UE 202 from a source(R)AN 204 s to a target RAN 204 t using Xn when the AMF 218 is unchangedand the SMF 220 determines to keep the existing UPF 212 (e.g., the UPF212 which terminates the N3 interface in the NG Core Network (NGC)). Thepresence of IP connectivity between the source UPF 212 and target UPF212 is assumed.

The procedure (5300) includes handover preparation (5302) and handoverexecution (5304). The handover execution (5304) includes the forwardingof data (5306) from a source (R)AN 204 s to a target (R)AN 204 t. Thetarget (R)AN 204 t sends an N2 path switch request message (5308) to theAMF 218 that includes an indication that the UE 202 has moved to a newtarget cell, and a list of PDU sessions to be switched or removed.Depending on the type of target cell, the target (R)AN 204 t includesother information in the message (5308) for each PDU session to beswitched, including the Time of Last Data Activity parameter, and (R)ANinformation such as the N3 (R)AN Address and the N3 tunnel endpointidentifier. If the target (R)AN 204 t cannot support a QoS flows of aPDU session, the N2 path switch request message (5308) may include thelist of accepted QoS flows and the list of rejected QoS flows for thisPDU session.

Next, the AMF 218 sends a N11 Message (5310) to each SMF 220 associatedwith the lists of PDU sessions received in the N2 Path Switch Request(5308) message. For the PDU sessions that require a path switch, uponreceipt of the N11 Message (5310), each of these SMFs 220 determinewhether or not the existing UPF 212 can continue to serve the UE 202. Ifthe existing UPF 212 cannot continue to serve the UE 202 and it is not aPDU session anchor, steps (5608) to (5624) of FIG. 56, as describedbelow, are performed. Otherwise, the following steps (5312) to (5318)are performed by each of these SMFs 220 if their existing UPFs 212 cancontinue to serve the UE 202. For each PDU session where a path switchis required, the SMF 220 determines whether or not the existing UPF 212is to be updated with the (R)AN tunnel information.

Next, the SMF 220 initiates a release of PDU sessions which are notrequested by the target RAN 204 t. For PDU sessions requested by thetarget RAN 204 t, the SMF 220 sends a N4 Session Modification Request(5312) message to the UPF 212. The message (5312) includes the (R)ANaddress, tunnel identifiers for the downlink user plane, and a list ofaccepted flows if present. For the PDU sessions where the (R)AN 204information does not need to be updated, the SMF 220 sends an N4 SessionModification Request (5312) message to the UPF 212 for these PDUsessions. The message (5312) indicates the release of RAN N3 tunnelinformation, such as the (R)AN address and Tunnel Endpoint Identifierfor the downlink user plane. Next, the UPF 212 returns an N4 SessionModification Response (5314) message to the SMF 220 after the requestedPDU sessions are switched or modified. The message (5314) includestunnel identifiers for uplink traffic. In order to assist the reorderingfunction in the target (R)AN 204 t for PDU sessions requiring a pathswitched, the UPF 212 sends one or more “end marker” packets (5316) onthe old path immediately after switching the path. The UPF 212 may startsending downlink packets (5318) to the target RAN 204 t. It is notedthat step (5318) can occur any time after receipt of the N4 SessionModification Response (5314) message at the SMF 2200. The SMF 220 sendsan N11 message acknowledgement (ACK) (5318) message to the AMF 212 forPDU sessions which have been switched or successfully modified. Themessage (5318) includes CN tunnel information. The message (5318)indicates whether the (R)AN N3 tunnel information is updated (e.g., apath switch) or released (e.g., a path release). In the SMF 220, for PDUsessions where the N3 (R)AN tunnel information is not updated in the UPF212, the N3 Connection Status parameter of these PDU sessions arechanged from N3_CONNECTED to N3_DISCONNECTED.

In the AMF 218, upon receiving the N11 Message ACK (5318), the N3Connection Status parameter of PDU sessions where the SMF 220 does notupdate the (R)AN information for the UPF 212 is changed fromN3_CONNECTED to N3_DISCONNECTED. Once the N11 Message ACK (5318) isreceived from all the SMFs 220, the AMF 218 aggregates the received CNTunnel Information from these responses and sends this aggregatedinformation as a part of a N2 SM Information in a N2 Path Switch RequestACK (5320) to the target (R)AN 204 t. The message (5320) includes anindication for each PDU session for whether or not the UPF 212 isupdated with (R)AN information. If none of the requested PDP sessionshave been successfully switched, the AMF 218 sends an N2 Path SwitchRequest Failure message to the target (R)AN 204 t. In the target (R)AN204 t, for PDU sessions where the UPF 212 is not updated with (R)ANinformation, the UPF N3 tunnel information is deleted. By sending aRelease Resources (5322) message to the source (R)AN 204 s, the target(R)AN 204 t confirms success of the handover. It then triggers therelease of resources with the source (R)AN 204 s.

FIG. 53 further illustrates, in a message flow diagram, an example of anXn based inter NG RAN handover procedure (5300) without User Planefunction relocation, in accordance with embodiments of the presentinvention. The Target (R)AN 204 may send an N2 Path Switch Requestmessage (5308) to an AMF 218 to inform that the UE 202 has moved to anew target cell, and to provide a list of PDU Sessions to be switched.Depending on the type of target cell, the Target (R)AN 204 t may includeappropriate information in this message. For each to be switched to theTarget (R)AN 204 t, the N2 Path Switch Request message (5308) mayinclude the list of accepted QoS flows.

The AMF 218 may then send N2 SM information by using an N11 Message(5310) to each SMF 220 associated with the list of PDU Sessions, and thelist of accepted QoS flows for each PDU session, received in the N2 PathSwitch Request (5308). For the PDU Sessions to be switched to the Target(R)AN 204 t, upon receipt of the N11 Message, each of the SMFs 220determine whether the existing UPF 212 can continue to serve the UE 202.If the existing UPF 212 cannot continue to serve the UE 202 and it isnot a PDU session anchor, steps 3-11 of clause 4.9.1.2 TS. 23.502 areperformed. Otherwise, the following steps are performed. For theactivated PDU session(s) which are not included in the N2 Path SwitchRequest message, the AMF 218 may send separate request(s) to therelevant SMF(s) 220.

For PDU Sessions requested by the Target (R)AN 204 t, the SMF 220 maysend a N4 Session Modification Request message (5312) to the UPF 212.The message (5312) may include the (R)AN address, the tunnel identifiersfor downlink User Plane, and the list of accepted QoS flows. For PDUSession that the Target (R)AN 204 t cannot support, the SMF 220 maydetermine whether to release or keep, but not to be switched, this PDUsession. If the PDU session is released, the SMF 220 may initiate thePDU Session Release procedure. If the PDU session is kept but not to beswitched, the SMF 220 may send an N4 Session Modification Request (5312)to the UPF 212 to set the Session-AMBR of the PDU session to zero.

For a PDU session to be switched, the UPF 212 may return an N4 SessionModification Response message (5314) to the SMF 212 after the requestedPDU Sessions are switched. The message (5314) may include the Tunnelidentifiers for uplink traffic. For PDU session to not be switched, theUPF 212 may return an N4 Session Modification Response message (5314)accordingly.

For a PDU session to be switched, in order to assist the reorderingfunction in the Target (R)AN 204 t, the UPF 212 may send one or more“end marker” packets (5316) on the old path after switching the path.The UPF 212 may start sending downlink packets to the Target (R)AN 204t.

The SMF 220 may then send an N11 Message ACK message (5318) to the AMF218 for PDU Sessions which have been switched successfully. The message(5318) may include the CN Tunnel Information. For a PDU session to notbe switched, the SMF 220 may send a N11 Message ACK (5318) to the (R)AN204 via the AMF 218. The message (5318) may include the N2 SM messagethat includes the PDU Session ID, and sets the Session-AMBR to 0. It isnoted that step (5318) can occur any time after receipt of N4 SessionModification Response at the SMF 220.

Once the N11 Message Response (5318) is received from all the SMFs 220,the AMF 218 may aggregate the received CN Tunnel Information from theseresponses and send the aggregated information as a part of N2 SMInformation in a N2 Path Switch Request ACK (5320) to the Target (R)AN204 t. If none of the requested PDP Sessions have been switchedsuccessfully, the AMF 218 may send an N2 Path Switch Request Failuremessage (5320) to the Target (R)AN. By sending a Release Resourcesmessage (5322) to the Source (R)AN 204 s, the Target (R)AN 204 t mayconfirm the success of the handover. It then may trigger the release ofresources with the Source (R)AN 204 s.

In an Inter NG-RAN node handover without Xn interface, a source (R)AN(S-RAN) 204 s may initiate an N2-based handover to the target (R)AN(T-RAN) 204 t. This can be triggered, for example, due to new radioconditions or load balancing, no Xn connectivity to the target (R)AN 204t, an error indication from the target (R)AN 204 t after an unsuccessfulXn-based handover, or based on dynamic information learnt by the S-RAN204 s.

FIG. 54 illustrates, in a flowchart, an example of a method (5400) ofhanding over a UE 202 from a source RAN 204 s to a target RAN 204 t, inaccordance with the Xn based inter NG RAN handover procedure (5300) ofFIG. 53. The method (5400) may be performed by the AMF 218. The method(5400) comprises the AMF 218 configured to receive the N2 path switchrequest (5308) message from the target RAN 204 t. Next, the AMF 218sends the N11 message (5310) to the SMF 220. Next, the AMF 218 receivesthe N11 message ACK (5318) from the SMF 220. Next, the AMF 218 sends theN2 path switch request ACK (5320) message to the target RAN 204 t. Othersteps may be added to the method (5400).

FIG. 55 illustrates, in a flowchart, another example of a method (5500)of handing over a UE 202 from a source RAN 204 s to a target RAN 204 t,in accordance with the Xn based inter NG RAN handover procedure (5300)of FIG. 53. The method (5500) may be performed by the SMF 220. Themethod (5500) comprises the SMF 220 configured to receive the N1 message(5310) from the AMF 218. Next, the SMF 220 sends the N4 sessionmodification request (5312) message to the UPF 212. Next, the SMF 220receives the N4 session modification response (5314) from the UPF 212.Next, the SMF sends the N11 message ACK (5318) to the AMF 218. Othersteps may be added to the method (5500).

FIG. 56 illustrates, in a message flow diagram, an example of a Xn basedinter NG RAN handover procedure (5600) with user plan functionrelocation, in accordance with an embodiment of the present invention.The procedure (5600) may be used to hand over a UE 202 from a source RAN204 s to a target RAN 204 t using Xn when the AMF 218 is unchanged andthe SMF 220 decides that the source UPF 212 s is to be released. Thesource UPF 212 s is the UPF 212 which terminates a N3 interface in theNGC. The presence of an IP connectivity between the source UPF 212 s andsource RAN 204 s, and between the target UPF 212 t and target RAN 204 tis assumed.

The procedure (5600) includes the handover preparation (5302) and thehandover execution (5304). The handover execution (5304) includes theforwarding of data (5306) from a source RAN 204 s to a target RAN 204 t.The target RAN 204 t may check whether some PDU sessions having a N3Status Flag “N3_AT_UPF_UPDATED” but having no data activity in thesource RAN 204 s by reading the parameter “Time of Last Data Activity”in the PDU session context. If the duration that a PDU has no dataactivity is longer than the parameter Session Inactive Timer, the PDUsession is considered as having no data activity. The target RAN 204 tmay send downlink data (5602) to the UE 202. The UE 202 may send uplinkdata (5604). The target RAN 204 t may send an N2 path switch requestmessage (5308) to an AMF 218 to inform that the UE 202 has moved to anew target cell, and a list of PDU sessions to be switched or removed, alist of PDU sessions that have no data activity marked by the target RAN204 t and a list of PDU sessions that have no data activity marked bythe source RAN 204 s. Depending on the type of target cell, the targetRAN 204 t may include appropriate information in this message (5308) foreach PDU session, including RAN type, N3 RAN Address and N3 tunnelendpoint identifier. If the target RAN 204 t cannot support some QoSflows of a PDU session, the N2 path switch request message (5308) mayinclude the list of accepted QoS flows and the list of rejected QoSflows for this PDU session.

Next, the AMF 218 may send a N11 message (5310) to each SMF 220associated with the lists of PDU sessions received in the N2 path switchrequest (5308). For the PDU sessions that require a path to be switched,upon receipt of the N11 message (5310), each of these SMFs 220determines whether the existing UPF 212 can continue to serve the UE202. If the existing UPF 212 cannot continue to serve the UE 202 and itis not a PDU session anchor, steps (5606) to (5624), as described below,are performed. Otherwise, the steps (5312) to (5318) of FIG. 53, asdescribed above, are performed by each of these SMFs 220 if theirexisting UPFs 212 can continue to serve the UE 202. For the PDU sessionsthat are in the list of PDU sessions having no data activity marked bythe source RAN 204 s and the list of PDU sessions having no dataactivity marked by target RAN 204 t, the AMF 218 may store the RAN 204information. For each PDU session in the list of PDU sessions having nodata activity marked by the target RAN 204 t, the AMF 218 may send theN11 message (5310) to the SMF 220 to forward the PDU Session ID tonotify that the PDU session has no data activity.

The SMF 220 may initiate the release of PDU sessions which are notrequested by the target RAN 204 t. The SMF 220 may then select a newtarget UPF 212 t (5606) based on UPF Selection Criteria according toclause 6.3.3 of TS 23.501. The target UPF 212 t IP address assignmentand allocation of downlink and uplink tunnel identifiers may beperformed by the SMF 220. An N4 session establishment request (includingthe target RAN 204 t address, uplink and downlink tunnel identifiers)message (5608) may be sent to the target UPF 212 t. The target UPF 212 tmay send an N4 session establishment response message (5610) to the SMF220. The SMF 220 may start a timer, to be used in step (5622) below. TheSMF 220 may send a N4 session modification request message (5612) to thePDU session anchor 212 a. The PDU session anchor 212 a may respond witha N4 session modification response message (5614). At this point, thePDU session anchor 212 a may start sending downlink packets (5616) tothe target RAN 204 t using the address and tunnel identifiers of thetarget RAN 204 t via the target UPF 212 t.

The SMF 220 may send a N11 message ACK (5618) (including CN tunnelinformation) to the AMF 218. After receiving the N11 message response(5618) from the SMF 220, for PDU sessions having no data activity markedby the target RAN 204 t, the AMF 218 may change the parameter N3 StatusFlag of these PDU sessions from N3_AT_UPF_UPDATED toN3_AT_UPF_NOT_UPDATED. Once the N11 message response (5618) is receivedfrom all the SMFs 220, the AMF 218 may aggregate the received CN tunnelinformation from these responses and send this aggregated information asa part of N2 SM information in a N2 path switch request ACK (5320) tothe target RAN 204 t. If none of the requested PDP sessions have beenswitched successfully, the AMF 218 may send an N2 path switch requestfailure message to the target RAN 204 t. In the target RAN 204 t, forPDU sessions having no data activity marked by the target RAN 204 t, theparameter N3 Status Flag of these PDU sessions may be changed fromN3_AT_UPF_UPDATED to N3_AT_UPF_NOT_UPDATED. By sending a releaseresources message (5322) to the source RAN 204 s, the target RAN 204 tconfirms success of the handover. It then triggers the release ofresources with the source RAN 204 s. The UE 202 may now send uplink data(5620). Once the timer has expired after step (5610), the SMF 220 mayinitiate a source UPF 212 s release procedure by sending an N4 sessiontermination request (5622) (including a release cause). The source UPF212 s may acknowledge with an N4 session termination response message(5624) to confirm the release of resources.

FIG. 56 further illustrates, in a message flow diagram, an example of aXn based inter NG (R)AN handover procedure (5600) with user planfunction relocation, in accordance with embodiments of the presentinvention. The procedure (5600) may be used to hand over a UE 202 from asource (R)AN 204 s to a target (R)AN 204 t using Xn when the AMF 218 isunchanged and the SMF 220 determines that the source UPF 212 s is to berelocated. The source UPF 212 s is the UPF 212 which terminates a N3interface in the NGC. The presence of an IP connectivity between thesource UPF 212 s and source RAN 204 s, and between the target UPF 212 tand target RAN 204 t, is assumed.

The procedure (5600) includes the handover preparation (5302) and thehandover execution (5304). The handover execution (5304) includes theforwarding of data (5306) from a source (R)AN 204 s to a target (R)AN204 t. The target (R)AN 204 t sends an N2 path switch request message(5308) to the AMF 218 that includes an indication that the UE 202 hasmoved to a new target cell, and a list of PDU sessions to be switched orremoved. Depending on the type of target cell, the target (R)AN 204 tincludes other information in the message (5308) for each PDU session tobe switched, including the Time of Last Data Activity parameter, and(R)AN information such as the N3 (R)AN Address and the N3 tunnelendpoint identifier. If the target (R)AN 204 t cannot support a QoSflows of a PDU session, the N2 path switch request message (5308) mayinclude the list of accepted QoS flows and the list of rejected QoSflows for this PDU session.

Next, the AMF 218 sends a N11 Message (5310) to each SMF 220 associatedwith the lists of PDU sessions received in the N2 Path Switch Request(5308) message. For the PDU sessions that require a path switch, uponreceipt of the N11 Message (5310), each of these SMFs 220 determinewhether or not the existing UPF 212 can continue to serve the UE 202. Ifthe existing UPF 212 cannot continue to serve the UE 202 and it is not aPDU session anchor, the following steps (7202608) to (5624) areperformed. Otherwise, steps (5312) to (5318) of FIG. 53, as describedabove, are performed are performed by each of these SMFs 220 if theirexisting UPFs 212 can continue to serve the UE 202. For each PDU sessionwhere a path switch is required, the SMF 220 determines whether or notthe existing UPF 212 is to be updated with the (R)AN tunnel information.

The SMF 220 initiates the release of PDU sessions which are notrequested by the target RAN 204 t. For PDU sessions to be switched, theSMF 220 then selects a new target UPF 212 t (5606) based on the UPFSelection Criteria according to clause 6.3.3 of TS 23.501. The targetUPF 212 t IP address assignment and allocation of downlink and uplinktunnel identifiers may be performed by the SMF 220. The SMF 220 sends anN4 Session Establishment Request (5608) message to the target UPF 212 t.The message (5608) includes the target RAN 204 t address, and uplink anddownlink tunnel identifiers. The target UPF 212 t sends an N4 SessionEstablishment Response (5610) message to the SMF 220. The SMF 220 maystart a timer, to be used in step (5590) below. The SMF 220 sends a N4Session Modification Request (5550) message to the PDU session anchor212 a. The PDU session anchor 212 a responds with a N4 SessionModification Response (5614) message. At this point, the PDU sessionanchor 212 a may start sending downlink packets (5616) to the target RAN204 t using the address and tunnel identifiers of the target RAN 204 tvia the target UPF 212 t.

The SMF 220 sends a N11 Message ACK (5618) to the AMF 218. The message(5618) includes the CN tunnel information. In the AMF 218, uponreceiving the N11 Message ACK (5318), the N3 Connection Status parameterof PDU sessions where the SMF 220 does not update the (R)AN informationfor the UPF 212 is changed from N3_CONNECTED to N3_DISCONNECTED. Oncethe N11 Message ACK (5318) is received from all the SMFs 220, the AMF218 aggregates the received CN Tunnel Information from these responsesand sends this aggregated information as a part of a N2 SM Informationin a N2 Path Switch Request ACK (5320) to the target (R)AN 204 t. Themessage (5320) includes an indication for each PDU session for whetheror not the UPF 212 is updated with (R)AN information. If none of therequested PDP sessions have been successfully switched, the AMF 218sends an N2 Path Switch Request Failure message to the target (R)AN 204t. In the target (R)AN 204 t, for PDU sessions where the UPF 212 is notupdated with (R)AN information, the UPF N3 tunnel information isdeleted. By sending a Release Resources (5322) message to the source(R)AN 204 s, the target (R)AN 204 t confirms success of the handover. Itthen triggers the release of resources with the source (R)AN 204 s.

Once the timer has expired after step (7302610), the SMF 220 initiates asource UPF 212 s release procedure by sending an N4 Session TerminationRequest (5622) message to the source UPF 212 s. The message (5622)includes a release cause. The source UPF 212 s acknowledges with an N4Session Termination Response (5624) message that indicates the releaseof resources.

FIG. 57 illustrates, in a message flow diagram, an example of a N3reconnection procedure (5700) triggered by UL data (i.e., a new UL datapacket), in accordance with an embodiment of the present invention. Thisprocedure (5700) may be used to trigger a path switch update for a PDUsession that has N3 Status Flag as N3_AT_UPF_NOT_UPDATED in the (R)AN204 when the uplink data arrives at the (R)AN 204. The UE 202 may send aUL data channel grant request or a UL data packet to the (R)AN 204(5702). If the N3 Status Flag of the PDU session isN3_AT_UPF_NOT_UPDATED, the (R)AN 204 may send a N2 message Path SwitchRequest (5704) to the AMF 218. The message (5704) may include the PDUsession ID (such as SUPI) and (R)AN information, including a (R)AN type,a N3 (R)AN Address and a N3 Tunnel Endpoint Identifier. Alternatively,the message (5704) may include the PDU Session ID only.

The AMF 218 may send a N11 message Path Switch Request (5706) to the SMF220 to forward the N2 message (5704) received from the (R)AN 204. Themessage (5706) may also include an identifier to identify the UE 202(such as 5G temporary ID or SUPI), and (R)AN information (such as (R)ANtype, N3 (R)AN Address and the N3 Tunnel Endpoint Identifier). The SMF220 may send a N4 message Session Modification Request (5708) to theUPF212. The message (5708) may include an identifier to identify the UE202 (such as 5G temporary ID or SUPI), the PDU session ID, the (R)ANtunnel information (such as N3 (R)AN Address and the N3 Tunnel EndpointIdentifier). The UPF 212 may update the (R)AN 204 information for therequested PDU session. The UPF 212 may send a N4 message SessionModification Response (5710) to the SMF 220. The message (5710) mayinclude the UE identifier (such as SUPI) and the PDU Session ID. The SMF220 may change the N3 Status Flag of the PDU session toN3_AT_UPF_UPDATED. The SMF 220 may send a N11 message Path SwitchResponse (5712) to the AMF 218. The message (5712) may include the UEidentifier (such as SUPI) and the PDU Session ID. The AMF 218 may changethe N3 Status Flag of the PDU session to N3_AT_UPF_UPDATED. The AMF 218may send a N2 message Path Switch Response (5714) to the (R)AN 204 toconfirm the path switch is complete. The message (5714) may include thePDU Session ID. The (R)AN 204 may then send uplink data packets (5716).

FIG. 57 further illustrates, in a message flow diagram, an example of alate path switch procedure (5700) triggered by UL data without a UPF 212relocation, in accordance with embodiments of the present invention.This procedure (5700) may be used to trigger a path switch update for aPDU session that has no UPF N3 tunnel information when the (R)AN 204receives the UL grant request or UL data for a PDU session. The UPF 212remains the same. The SMF 220 stores the CN tunnel information. The UE202 sends a UL Data Channel Grant Request or a UL Data Packet to the(R)AN 204 for a PDU session (5702). If the UPF N3 tunnel information isnot available, the (R)AN 204 sends a N2 Message Session Path SwitchRequest (5704) to the AMF 218. The message (5704) includes the PDUsession ID and (R)AN tunnel information, such as a (R)AN N3 Address anda N3 Tunnel Endpoint Identifier.

The AMF 218 sends a N11 Message Session Path Switch Request (5706) tothe SMF 220. The message (5706) includes an identifier to identify theUE 202 (such as a SUPI and PDU Session ID, and the (R)AN tunnelinformation (such as the (R)AN type, the N3 (R)AN Address and thedownlink Tunnel Endpoint Identifier. The SMF 220 determines whether ornot the existing UPF 212 can continue to serve the UE's PDU sessions. Ifthe existing UPF 212 cannot continue to serve the UE 202 and it is not aPDU session anchor, steps (4) to (9) of clause 4.9.1.c of TS 23.502 areperformed. If the existing UPFs 212 can continue to serve the UE 202,the SMF 220 sends a N4 Message Session Modification Request (5708)message to the UPF212. The message (5708) includes a UE identifier (suchas a SUPI), the PDU session ID, and the N3 (R)AN tunnel information,such as a N3 (R)AN Address and the N3 Tunnel Endpoint Identifier. TheUPF 212 updates the (R)AN 204 tunnel information for the requested PDUsession. The UPF 212 sends a N4 Message Session Modification Response(5710) message to the SMF 220. The message (5710) includes the SUPI andthe PDU session ID. The SMF 220 sends a N11 Message Path Switch Response(5712) to the AMF 218. The message (5712) includes the UE identifier(such as a SUPI), the PDU session ID, and the N2 SM Message thatincludes the CN tunnel information for the (R)AN 204. The SMF 220changes the N3 Connection Status of the PDU session to N3_CONNECTED. TheAMF 218 sends a N2 Message Path Switch Response (5714) message to the(R)AN 204 that indicates that the path switch is complete. The message(5714) includes the PDU Session ID, and the N2 SM Message received fromthe SMF 220. THE AMF 218 changes the N3 Connection Status of the PDUsession to N3_CONNECTED. The (R)AN 204 updates the CN tunnel informationand sends uplink data (5716) packets.

FIG. 58 illustrates, in a message flow diagram, an example of a N3reconnection procedure (5800) triggered by DL data (i.e., a new DL datapacket), in accordance with an embodiment of the present invention. Thisprocedure (5800) may be used to trigger a path switch update at the UPF212 for a PDU session that has the N3 Status Flag asN3_AT_UPF_NOT_UPDATED in the SMF 220 when the downlink data arrives atthe UPF 212. The UPF 212 may receive downlink data packets from the DN208 (5802). The UPF 212 may send N4 message DL data notification (5804)to the SMF 220. The message (5804) may include an identifier to identifythe UE 202 (such as 5G temporary or SUPI) and a PDU Session ID.

Based on the N3 Status Flag currently set as N3_AT_UPF_NOT_UPDATED, theSMF 220 may send a N11 message (R)AN Information Request (5806) to theAMF 218. The message (5806) may include the UE Identifier (such as SUPI)and the PDU Session ID. The AMF 218 may change the N3 Status Flag of thePDU session to N3_AT_UPF_UPDATED. The AMF 218 may send a N11 message(R)AN Information Response (5808) to the SMF 220. The message (5808)includes an UE identifier (such as SUPI), the PDU session ID, and (R)ANinformation (including the (R)AN type, the N3 (R)AN address, and the N3(R)AN tunnel endpoint identifier). The SMF 220 may send a N4 messageSession Modification Request (5810) to the UPF 212. The message (5810)may include an identifier to identify the UE 202 (such as 5G temporaryID or SUPI), the PDU Session ID, the (R)AN information (such as N3 (R)ANAddress and the N3 Tunnel Endpoint Identifier). The UPF 212 may updatethe (R)AN 204 information for the requested PDU session. The UPF 212 maysend a N4 message Session Modification Response (5812) to the SMF 220.The message (5812) may include the UE identifier (such as SUPI) and thePDU Session ID. After receiving the message (5690), the SMF 220 maychange the N3 Status Flag of the PDU session to N3_AT_UPF_UPDATED. TheUPF 212 may send downlink data packets (5814) to the UE 202 via the(R)AN 204. It is noted that step (5814) may be performed before step(5812).

In an alternative implementation of FIG. 58, after receiving message(5806), the AMF 218 may send an N2 Notification message to the (R)AN 204informing that the UPF 212 is updated with the (R)AN information. Themessage may include the PDU Session ID. The (R)AN 204 may change the N3Status Flag of the PDU session to N3_AT_UPF_UPDATED. The (R)AN 204 maysend a N2 message Notification Acknowledgment to the AMF 218 confirmingthe reception of the Notification message from the AMF 218.

In another alternative implementation of FIG. 58, after receivingmessage (5812), the SMF 220 may send an N2 message to the (R)AN 204 viathe AMF 218 to notify the (R)AN 204 that the UPF 212 has updated (R)ANinformation. The message may include the PDU Session ID. After receivingthis message, the (R)AN 204 may change the N3 Status Flag of the PDUsession to N3_AT_UPF_UPDATED.

(R)AN-CN interactions include procedures that pertain to N2 (e.g., NG2)interactions, e.g., a N2 release procedure and potential procedures fora RRC Connected Inactive state.

An N2 Release procedure may be used to release the logical N2 signallingconnection and all N3 connections for a UE 202. The procedure willtransition the UE 202 from a CN-CONNECTED state to a CN-IDLE state inboth the UE 202 and the AMF 218. That is, the UE context in the UE 202and the AMF 218 will be changed accordingly. All UE related contextinformation will be removed in the (R)AN 204.

When a N2 signalling connection is lost, for example, due to the loss ofthe signalling transport or because of a (R)AN failure, the N2 releaseprocedure may be performed locally by the (R)AN 204 and the AMF 218.When the N2 release procedure is performed locally by the (R)AN 204 orthe AMF 218, each node locally performs its actions as described in theprocedure flow below without using or relying on any of the signallingshown directly between the (R)AN 204 and the AMF 218. It should be notedthat when the N2 signalling connection is lost due to AMF 218 failure,it may be resolved through resolving the N2 stickiness and not result ina N2 release. The initiation of a N2 Release procedure may be either(R)AN-initiated with a cause, or AMF-initiated with a cause. The causeof a (R)AN-initiated procedure may be at least one of an O&MIntervention, an Unspecified Failure, User Inactivity, Repeated RRCsignalling Integrity Check Failure, a Release due to a UE generatedsignalling connection release, an Inter-RAT Redirection, etc. The causeof an AMF-initiated procedure may be at least one of an authenticationfailure, a detach, etc.

The N2 Release procedure may be used to release a N2 connection and atthe same time deactivate PDU sessions when the UE 202 enters the CM-IDLEstate. FIG. 59 illustrates, in a message flow diagram, an example of aN2 Release and PDU Session deactivation procedure (5900), in accordancewith embodiments of the present invention. The procedure (5900) maybegin with the (R)AN 204 and the UE 202 performing a RRC Releaseprocedure (5902). The RRC Release procedure (5902) may be similar to theRRC Release procedure (600A) describe above. The (R)AN 204 interactswith the UE 202 to release the RRC signalling connection. The UE 202enters the CM-IDLE state and deactivates all PDU sessions. The (R)AN 204may send (N2 message) a N2 Release Request (5904) to the AMF 218. Themessage (5904) may include a cause code, such as an O&M intervention, UEinactivity, etc. Those skilled in the art will appreciate that, incertain scenarios, step (5902) can be initiated before or in parallelwith step (5904). The AMF 218 may send (N11 message) a N2 ReleaseNotification message (5906) to the SMF(s) 220 which have subscribed tothe N2 Release Notification. The message (5906) may include a UEidentifier (such as a SUPI), the RAN information, and the cause code. Itshould be noted that the SMF 220 may subscribe to a UE mobility EventNotification service of the AMF 218 by default when the PDU session isestablished or activated. In this message, the AMF 218 will notify theSMF 220 of the N2 Release event. The AMF 218 may track, or otherwise beaware of, the session state, i.e., whether or not the session isactivated. The AMF 218 informs the SMF(s) 220 that serve activated PDUsessions of the session state.

The SMF 220 then sends (N4 message) a N3 Release Request (5908) to theUPF(s) 212. The message (5908) may include a UE SUPI and PDU SessionID(s) to be deactivated. The UPF 212 then releases the N3 (R)AN tunnelinformation (e.g., the (R)AN IP address and tunnel identifier) in theUE's PDU Session Context of PDU sessions to be deactivated. The UPFsends (N4 message) a N3 Release Response (5910) to the SMF 220confirming the release of the N3 (R)AN tunnel information. The UPF 212may begin to buffer downlink packets of the deactivated PDU sessions.The SMF 220 then sends (N11 message) a PDU Session Event ReportNotification (5912) to the AMF 218 to inform the AMF 218 that the (R)ANtunnel information is deleted in the UPF 212. This message (5912) is toacknowledge the N2 release notification message (5906). The SMF 220 maythen change the state of the PDU session to Session-IDLE.

The AMF 218 then collects all the responses from the SMF(s) 220 thatwere notified in (5906). Once all the acknowledgements from the SMF 220are collected, and if step (5902) is not performed, the AMF 218 thensends (N2 message) a N2 Release Response (5914) to the (R)AN 204 with acause code. The AMF 218 may change the session state of all PDU sessionsof the UE 202 to Session-IDLE. If step (5902) was not performed, the RAN204 and the UE 202 perform a RRC Release procedure (5916). The RRCRelease procedure (5916) may be similar to the RRC Release procedure(600A) describe above. The (R)AN 204 sends a message to UE 202 torelease the RRC connection. The UE 202 enters the CM-IDLE state and allPDU sessions in the UE 202 transition to the Session-IDLE state. Uponreceiving RRC connection release confirmation from the UE 202, the (R)AN204 removes the UE Context. Next, the (R)AN 204 sends (N2 message) a N2Release Confirmation (5918) to the AMF 218. Upon receiving the N2Release Response (5918) message, the AMF 218 sets the UE Context to theCM-IDLE state and releases the N2 connection. It should be noted thatthe AMF 218 may remove the subscription to UE Mobility EventNotification service of the AMF 218 for the SMF(s) service PDU sessions.

In a modification to the embodiment described with respect to FIG. 59,the N2 Release procedure may be used to release a N2 connection and atthe same time deactivate PDU sessions when the UE 202 enters the CM-IDLEstate. FIG. 60 illustrates, in a message flow diagram, another exampleof a N2 Release and PDU Session deactivation procedure (6000), inaccordance with embodiments of the present invention. The procedure(6000) may begin with the (R)AN 204 and the UE 202 performing a RRCRelease procedure (5902). The RRC Release procedure (5902) may besimilar to the RRC Release procedure (600A) describe above. The (R)AN204 interacts with the UE 202 to release the RRC signalling connection.The UE 202 enters the CM-IDLE state and deactivates all PDU sessions.The (R)AN 204 may send (N2 message) a RRC Release Notification (5904) tothe AMF 218. The message (6002) may include a cause code, such as an O&Mintervention, UE inactivity, etc. Those skilled in the art willappreciate that, in certain scenarios, step (5902) can be initiatedbefore or in parallel with step (6002). The AMF 218 may send (N11message) a N2 Release Notification message (6004) to the SMF(s) 220which have subscribed to the N2 Release Notification. The message (6204)may include a UE identifier (such as SUPI), the RAN information, and thecause code. It should be noted that the SMF 220 may subscribe to a N2Release Notification service by default when the PDU session isestablished or activated. The AMF 218 may track, or otherwise be awareof, the session state, i.e., whether or not the session is activated.The AMF 218 informs the SMF(s) 220 that serve activated PDU sessions ofthe session state.

The SMF 220 then sends (N4 message) a N3 Release Request (6006) to theUPF(s) 212. The message (6006) may include a UE identifier (such asSUPI) and PDU Session ID(s) to be deactivated. The UPF 212 then releasesthe N3 (R)AN tunnel information (e.g., the (R)AN IP address and tunnelendpoint identifier) in the UE's PDU Session Context of PDU sessions tobe deactivated. The UPF sends (N4 message) a N3 Release Response (6008)to the SMF 220 confirming the release of the N3 tunnel information. TheUPF 212 may begin to buffer downlink packets of the deactivated PDUsessions. The SMF 220 then sends (N11 message) a N2 Release NotificationAcknowledgement (6010) message to the AMF 218 that acknowledges therelease notification message (6004). The SMF 220 may then change thestate of the PDU session to Session-IDLE.

The AMF 218 then collects all the responses from the SMF(s) 220 thatwere notified in (6004). Once all the acknowledgements from the SMF 220are collected, and if step (5902) is not performed, the AMF 218 thensends (N2 message) a N2 Release Request (6012) message to the (R)AN 204with a cause code. The AMF 218 changes the session state of all PDUsessions of the UE 202 to Session-IDLE. If step (5902) was notperformed, the (R)AN 204 and the UE 202 perform a RRC Release procedure(5916). The RRC Release procedure (5916) may be similar to the RRCRelease procedure (600A) describe above. The (R)AN 204 sends a messageto UE 202 to release the RRC connection. The UE 202 enters the CM-IDLEstate and all PDU sessions in the UE 202 transition to the Session-IDLEstate. Upon receiving RRC connection release confirmation from the UE202, the RAN 204 removes the UE Context. Next, the (R)AN 204 sends (N2message) a N2 Release Response (6014) to the AMF 218. Upon receiving theN2 Release Response (6014) message, the AMF 218 sets the UE Context tothe CM-IDLE state and releases the N2 connection.

A UE 202 or network requested PDU session release for non-roaming androaming with local breakout procedure may be used to release a PDUsession when the UE 202 is in the CM-CONNECTED state. FIG. 61illustrates, in a message flow diagram, an example of a PDU sessionrelease procedure (6100) triggered by the UE 202, PCF 222, or the SMF220, in accordance with embodiments of the present invention. Onetrigger for the PDU session release procedure (6100) occurs when the UE202 sends to the SMF 220 the (N1 SM message) UE Session Release Request(6102) message. The message (6102) may include the PDU Session ID. The(R)AN 204 forwards the message over a logical interface, such as a N2connection. The AMF 218 checks the PDU session ID and forwards themessage to the SMF 220. The forwarded message from the AMF 218 to theSMF 220 includes a UE identifier (such as SUPI) and a N1 message PDUSession Release Request. Another trigger for the PDU session releaseprocedure (6100) occurs when the PCF 222 sends to the SMF 220 a N7message PCF Session Release Request (6104) message. Another trigger forthe PDU session release procedure (6100) occurs when the SMF 220determines to release a PDU sessions by its own logic, or by takingrequests from at least one of the UE 202, AN 204 (e.g., congestionreport), DN 208, and UPF 212.

Once the PDU session release procedure (6100) is triggered, the SMF 220interacts with the UPF 212 to release the PDU Context at the UPF 212.The SMF 220 sends a N4 Message Session Release Request (6108) message tothe UPF 212. The message (6108) may include at least one of a UEidentifier (such as SUPI) and the PDU Session ID. The UPF 212 drops anyremaining packets of the PDU session to be released and releases theUE's PDU Context. The UPF 212 then sends a (N4 message) Session ReleaseResponse (6110) message to the SMF 220. If a dynamic policy isimplemented, the SMF 220 informs the PCF 222 to perform a PDU-CAN PDUSession Release procedure (6112) so that the PCF 222 will not provideany further session modification messages to the SMF 220 pertaining tothe released PDU session. The SMF 220 knows whether or not the sessionstate is activated. The SMF 220 sends a N11 Message (6202) to the AMF218, which includes an UE ID (e.g., a SUPI), a N1 SM PDU Session ReleaseRequest to the UE 202, and a N2 SM PDU Session Release Request to the(R)AN 204 if the PDU session has been activated. The N1 SM PDU SessionRelease Request message may include the PDU Session ID(s) and the causecode(s). The N2 SM PDU Session Release Request message may include thePDU Session ID(s). The N1 SM and N2 SM messages may be encapsulated in acontainer. The SMF 220 may use a Message Transfer service of the AMF218, as defined in clause 5.2.2.4 of TS 23.502, to send the N1 SM and N2SM messages to the UE 202 and (R)AN 204.

The AMF 218 then transfers (6116) the message received from the SMF 220to the (R)AN 204 via a logical interface, such as the N2 connection. Ifthe (R)AN 204 receives the N1 SM PDU Session Release Request only, the(R)AN 204 forwards (6118) this message to the UE 202. If (R)AN 204receives the N1 SM PDU Session Release Request and the N2 SM PDU SessionRelease Request, the (R)AN 204 performs a RRC Connection Reconfigurationwith the UE 202. During this reconfiguration procedure, the (R)AN 204forwards the N1 SM message PDU Session Release Request to the UE 202.The (R)AN 204 and the UE 202 release the radio resource(s) for thereleased PDU session(s). The UE 202 and AN 204 release the PDU sessioncontext. If the (R)AN 204 receives the N2 SM PDU Session Release Requestin step (6224), the (R)AN 204 sends to the SMF 220 an N2 SM PDU SessionRelease Response (6120) via the AMF 218. The message (6120) may includethe PDU session ID(s). The AMF 218 sends a N11 Message (6122) to forwardthe N2 SM PDU Session Response to the SMF 220. The message (6122)includes a UE identifier (such as a SUPI) and the N2 SM PDU SessionResponse received from the (R)AN 204. After the UE 202 receives the N1SM message PDU Session Release Request in step (6118), the UE 202releases the resources serving the released PDU sessions and deletes thePDU session context. The UE 202 sends the N1 SM PDU Session ReleaseResponse (6124) to the SMF 220. The message includes the PDU SessionID(s). The (R)AN 204 transfers this message to the AMF 218 via a logicalinterface, such as the N2 connection. The AMF 218 sends a N11 Message toforward (6126) the N1 SM PDU Session Release Response received in step(6124) to the SMF 220. The N11 Message may include at least one of a UEidentifier (such as a SUPI) and the N1 SM PDU Session Release Responsereceived in step (6122). After receiving messages in steps (6122) and(6126), the SMF 220 sends a N11 Message PDU Session Event ReportNotification (62/046,128) message, as defined in Clause 5.2.8.1 of TS23.502, to the AMF 218 with the event trigger being a PDU sessionrelease. The SMF 220 and AMF 218 delete their PDU session context of thereleased PDU session.

As noted above, the procedure (6100) can be used to perform a PDUsession release triggered by the UE 202. Alternatively, the procedure(6100) may be used, with some modifications, as a network requested PDUsession release procedure for non-roaming and roaming with localbreakout to release a PDU session when the UE 202 is in the CM-IDLEstate. For example, if the UE 202 is in the CM-IDLE state, the AMF 218will send a paging message to the UE 202, carrying a notification torelease the PDU session and the PDU session ID to be released. Remainingsteps are similar to the procedure (6100). For example, the UE 202 sendsa N1 SM PDU Session Release Request to the SMF 220.

In a modification to the embodiment described with respect to FIG. 61, aUE 202 or network requested PDU session release for non-roaming androaming with local breakout procedure may be used to release a PDUsession when the UE 202 is in the CM-CONNECTED state or the CM-IDLEstate. The SMF 220 may be unaware of UE's connection management state,but knows whether or not the PDU session is activated. If the UE 202 isin the CM-IDLE state, the AMF 220 may send the PDU session status in theAMF 218 to the UE 202 for synchronization when the service requestprocedure takes place. FIG. 62 illustrates, in a message flow diagram,another example of a PDU session release procedure (6200) triggered bythe UE 202 or the SMF 220, in accordance with embodiments of the presentinvention. One trigger for the PDU session release procedure (6200)occurs when the UE 202 sends to the SMF 220 the (N1 SM message) UESession Release Request (6102) message. The message (6102) may includethe PDU Session ID. The (R)AN 204 forwards the message over a logicalinterface, such as a N2 connection. The AMF 218 checks the PDU sessionID and forwards the message to the SMF 220. The forwarded message fromthe AMF 218 to the SMF 220 includes a UE identifier (such as a SUPI) anda N1 message PDU Session Release Request. Another trigger for the PDUsession release procedure (6200) occurs when the PCF 222 sends to theSMF 220 a N7 message PCF Session Release Request (6104). Another triggerfor the PDU session release procedure (6100) occurs when the SMF 220decides to release a PDU sessions by its own logic, or by takingrequests from the UE 202, AN 204 (e.g., congestion report), DN 208, andUPF 212.

Once the PDU session release procedure (62006200) is triggered, the SMF220 interacts with the UPF 212 to release the PDU Context at the UPF212. The SMF 220 sends a N4 Message Session Release Request (6108) tothe UPF 212. The message (6108) may include at least one of a UEidentifier (such as a SUPI) and the PDU Session ID. The UPF 212 dropsany remaining packets of the PDU session to be released and releases theUE's PDU Context. The UPF 212 then sends a (N4 message) Session ReleaseResponse (6110) to the SMF 220. If a dynamic policy is implemented, theSMF 220 informs the PCF 222 to perform a PDU-CAN PDU Session Releaseprocedure (6112). The SMF 220 knows whether or not the session state isactivated. The SMF 220 sends a N11 Message Session Release Notification(6202) to the AMF 218, which includes an UE ID (e.g., SUPI), a N1 SM PDUSession Release Request to the UE 202, and a N2 SM PDU Session ReleaseRequest to the (R)AN 204 if the PDU session has been activated. The N1SM PDU Session Release Request message may include the PDU Session ID(s)and the cause code(s). The N2 SM PDU Session Release Request message mayinclude the PDU Session ID(s)). The N1 SM and N2 SM messages may beencapsulated in a container. The SMF 220 may use a Message Transferservice of the AMF 218 to send the N1 SM and N2 SM messages to the UE202 and (R)AN 204.

If the UE is in the CM-CONNECTED state, then the AMF 218 transfers(6116) the message received from the SMF 220 to the (R)AN 204 via alogical interface, such as the N2 connection. If the (R)AN 204 receivesthe N1 SM PDU Session Release Request only, the (R)AN 204 forwards(6118) this message to the UE 202. If (R)AN 204 receives the N1 SM PDUSession Release Request and the N2 SM PDU Session Release Request, the(R)AN 204 performs a RRC Connection Reconfiguration with the UE 202.During this reconfiguration procedure, the (R)AN 204 forwards the N1 SMmessage PDU Session Release Request to the UE 202. The (R)AN 204 and theUE 202 release the radio resource(s) for the released PDU session(s).The UE 202 and (R)AN 204 release the PDU session context. If the (R)AN204 receives the N2 SM PDU Session Release Request in step (6116), the(R)AN 204 sends to the SMF 220 an N2 SM PDU Session Release Response(6120) via the AMF 218. The message (6120) may include the PDU sessionID(s). The AMF 218 sends a N11 Message (6275) to forward the N2 SM PDUSession Response to the SMF 220. The message (6275) includes the UEidentifier (such as a SUPI) and the N2 SM PDU Session Response receivedfrom the (R)AN 204. If the UE 202 receives the N1 SM message PDU SessionRelease Request in step (6118), then the UE 202 releases the resourcesserving the released PDU sessions and deletes the PDU session context.The UE 202 sends the N1 SM PDU Session Release Response (6122) to theSMF 220. The message includes the PDU Session ID(s). The (R)AN 204transfers this message to the AMF 218 via a logical interface, such asthe N2 connection. The AMF 218 sends a N11 Message to forward (6124) theN1 SM PDU Session Release Response received in step (6122) to the SMF220. The N11 Message may include at least one of a UE identifier (suchas a SUPI) and the N1 SM PDU Session Release Response received in step(6122). After receiving messages in steps (6275) and (6124), the SMF 220sends a N11 Message Session Release Confirmation (6204) to the AMF 218.The SMF 220 and AMF 218 delete their PDU session context of the releasedPDU session.

If the UE 202 is in the CM-IDLE state, the messages 6224, 6118, 6120,6275, 6122, 6124, and 6204 are skipped. The AMF 218 sends a N11 MessagePDU Session Release Acknowledgment (6206) to the SMF 220.

A Service Request procedure may be used by a 5G UE 202 in the CM-IDLEstate to request the establishment of a secure connection to an AMF 218.The UE 202 in the CM-IDLE state may initiate the Service Requestprocedure to send uplink signalling messages, user data, or a responseto a network paging request. After receiving the Service Requestmessage, the AMF 218 may perform authentication, and the securityprocedure. After the establishment of a secure signalling connection toan AMF 218, the UE 202 or network may send signalling messages, e.g.,PDU session establishment from UE 202 to the core network 206, or theSMF 220, via the AMF 220, may start the user plane resourceestablishment for the PDU sessions requested by the network and/orindicated in the Service Request message.

For any Service Request, the AMF 218 may respond with a Service Responsemessage to synchronize PDU session status between the UE 202 and thecore network 206. The AMF 218 may also respond with a Service Rejectmessage to the UE 202, if the Service Request cannot be accepted by thenetwork. For a Service Request due to user data, a network may takefurther actions if a user plane resource establishment is notsuccessful. It should be noted that the service request procedurediscussed in FIG. 63 below is not applicable to an access network, suchas a WiFi network, (once the UE 202 is registered in the network) inwhich the UE 202 is always considered as in the CM-CONNECTED state andin which the user plane resource is always considered established for anactive PDU session.

FIG. 63 illustrates, in a message call diagram, an example of a Xn basedinter NG (R)AN handover procedure (6300) without user plane functionrelocation and with session deactivation, in accordance with embodimentsof the present invention. The procedure (6300) combines the handoverprocedure defined in clause 4.9.1.1 of TS 23.502 and the sessiondeactivation signalling messages. The procedure (6300) includes handoverpreparation (6302) and handover execution (6304). The handover execution(6304) includes the forwarding of data (6306) from a source (R)AN 204 sto a target (R)AN 204 t.

The target (R)AN 204 t sends an N2 Path Switch Request (6308) message toan AMF 218 that includes an indication that the UE 202 has moved to anew target cell, and a list of PDU Sessions to be switched or removed.Depending on the type of target cell, the target (R)AN 204 t includesappropriate information in this message. The PDU sessions to be switchedare the PDU sessions having UPF N3 tunnel information. For each PDUsession to be switched, the target (R)AN 204 t includes the Time of LastData Activity parameter, and (R)AN information, such as the N3 (R)ANAddress and the N3 tunnel endpoint identifier. If the target (R)AN 204 tcannot support some QoS flows of a PDU session, then the N2 Path SwitchRequest (6308) message includes the list of accepted QoS flows and thelist of rejected QoS flows for this PDU session.

The AMF 218 then sends a N11 Message (6310) to each SMF 220 associatedwith the list of PDU Sessions received in the N2 Path Switch Request(6308) message. For the PDU Sessions that require a path switch, uponreceipt of the N11 Message (6310), each of the SMFs 220 determineswhether or not the existing UPF 212 can continue to serve the UE 202. Ifthe existing UPF 212 cannot continue to serve the UE 202, and it is nota PDU session anchor, steps 3-11 of clause 4.9.1.2 of TS 23.502 areperformed. Otherwise, the following steps (6312) to (6322) are performedby each of the SMFs 220 if their existing UPFs 212 can continue to servethe UE 202. For each PDU session that the path switch is required, theSMF 220 determines whether or not to deactivate the session.

The SMF 220 initiates the release of PDU Sessions which are notrequested by the target (R)AN 204 t. For PDU Sessions requested by thetarget (R)AN 204 t, the SMF 220 sends to the UPF 212 an N4 SessionModification Request (6312) including the (R)AN address, tunnelidentifiers for the downlink user plane, and a list of accepted flows ifpresent. For the PDU sessions to be deactivated, the SMF 220 sends tothe UPF 212 the N4 Session Modification Request (6312) message for thesePDU sessions. The message (6312) indicates the release of (R)AN N3tunnel information including (R)AN Address and a Tunnel EndpointIdentifier for the downlink user plane. The UPF 212 returns an N4Session Modification Response (6314) message to the SMF 212 after therequested PDU Sessions are switched or modified. The message (6314)includes tunnel identifiers for uplink traffic. In order to assist thereordering function in the target (R)AN 204 t for the PDU sessionsrequiring a path switch, the UPF 212 sends one or more “end marker”packets (6316) on the old path immediately after switching the path. TheUPF 212 starts sending downlink packets (6318) to the target (R)AN 204t.

The SMF 220 sends to the AMF 218 an N11 Message ACK (6320) message forPDU Sessions which have been successfully switched. The message (6320)includes CN Tunnel Information, and indicates whether the (R)AN N3tunnel information is updated (e.g., path switched) or deactivated(e.g., path released). The N11 Message ACK (6320) includes the N2 SMMessage, including PDU session ID(s), for the (R)AN 204 to deactivatethe PDU Sessions. In the SMF 220, for PDU sessions that are deactivated,the Session State parameter is changed to Session-IDLE. It should benoted that step (6320) can occur any time after receipt of the N4Session Modification Response (6314) message at the SMF 220.

Upon receiving the N11 Message ACK (6320), the AMF 218 sets the sessionstate of PDU sessions accordingly. Once the N11 Message ACK (6320)response is received from all the SMFs 220, the AMF 218 aggregates thereceived CN Tunnel Information from these responses and sends thisaggregated information as a part of a N2 SM Information and N1 MessageSession Deactivation Request (including PDU Session ID(s) to bedeactivated) in N2 Path Switch Request ACK (6322) message to the targetRAN 204 t. If none of the requested PDP Sessions have been switchedsuccessfully, the AMF 218 sends an N2 Path Switch Request Failuremessage as the message (6322) to the target (R)AN 204 t. In the target(R)AN 204 t, for PDU sessions to be deactivated, the UPF N3 tunnelinformation is deleted. The (R)AN 204 t forwards a N1 Message SessionDeactivation Request (6324) message to the UE 202 in a RRC message. TheUE 202 sets the Session State of the PDU sessions indicated in the N1 SMMessage to Session-IDLE. The UE 202 releases the radio context of thedeactivated PDU sessions. The UE 202 sends a N1 Message SessionDeactivation Response (6326) message to the AMF 218, via the target(R)AN 204 t. By sending a Release Resources message (6328) to the sourceRAN 204 s, the target (R)AN 204 t confirms success of the handover. Itthen triggers the release of resources with the source RAN 204 s.

FIG. 64 illustrates, in a message flow diagram, an example of aUE-triggered Service Request procedure (6400), in accordance withembodiments of the present invention. The UE 202 may send to the (R)AN204 a MM NAS Service Request (6402) message that includes PDU sessionID(s), security parameters, and a PDU session status. The UE 202 sends aNAS message Service Request towards the AMF 218 encapsulated in an RRCmessage to the RAN 204. If the Service Request is triggered for userdata, the UE 202 includes the PDU session ID(s) in the NAS ServiceRequest message (6402) to indicate the PDU session(s) that the UE 202 isrequesting to use. If the Service Request is triggered for signallingonly, the UE 202 does not need to include any PDU session ID. When thisprocedure (6400) is triggered for a paging response, if the UE 202 needsto use some PDU session(s), the UE 202 includes those PDU session ID(s)in the MM NAS Service Request message (6402). Otherwise the UE 202 doesnot need to include any PDU session ID. The PDU session status indicatesthe PDU sessions available in the UE 202. The PDU session status isincluded if the UE 202 has released some PDU sessions but has notinformed the AMF 218 when the UE 202 is in the CM-IDLE state.

The (R)AN 204 then sends to the AMF 218 a N2 Message (6404) thatincludes the MM NAS Service Request, a 5G Temporary ID, locationinformation, a RAT type, and a RRC establishment cause. If the AMF 218is not able to handle the Service Request, it will reject it. A 5GTemporary ID is obtained in a RRC procedure. The RAN 204 selects the AMF218 according to this Temporary ID. The location information and the RATtype relates to the cell in which the UE 202 is camped. Based on the PDUsession status, the AMF 218 may initiate the PDU session releaseprocedure if the PDU session is not available in the UE 202.

If the Service Request was not sent integrity-protected, or if integrityprotection is indicated as having failed, the AMF 218 may initiate a NASauthentication/security procedure (6406). If the UE 202 triggered theService Request to establish a signalling connection only, then afterthe security exchange, the UE 202 and the network can send signalling.

If the MM NAS Service Request message includes PDU session ID(s), or ifthis procedure (6400) is triggered by the SMF 220 but the PDU sessionIDs from the UE 202 correlates to other SMFs 220 than the one triggeringthe procedure, the AMF 218 sends a N11 message (6408) to SMF(s) 220associated with the PDU session ID(s). After receiving the N11 Message(6408), each SMF 220 sends a N11 Message (6410) to the AMF 218 toestablish the user plane(s) for the PDU sessions. The message (6410)includes N2 SM information such as a QoS profile, and CN N3 tunnelinformation). The N2 SM information includes information that the AMF220 may provide to the RAN 204.

The AMF 218 may send to the (R)AN 204 a N2 Request (6412) message thatincludes the N2 SM information received from the SMF 220, a securitycontext, an AMF Signalling Connection ID, a Handover Restriction List,and a MM NAS Service Accept. The RAN 204 stores the Security Context,AMF Signalling Connection Id, QoS Information for the QoS Flows of thePDU Sessions that are activated, and N3 Tunnel IDs in the UE RANcontext. The MM NAS Service Accept includes the PDU session status inthe AMF 218. The PDU session status is included if the core network hasreleased some PDU sessions but has not informed the UE 202 when the UE202 is in the CM-IDLE state. The AMF 218 may include at least one N2 SMinformation element from the SMF 220 if the procedure (6400) istriggered for PDU session user plane setup. The AMF 218 may sendadditional N2 SM information from the SMFs 220, if any, in separate N2message(s), such as a N2 tunnel setup request. Alternatively, ifmultiple SMFs 220 are involved, the AMF 218 may send one N2 Requestmessage to the (R)AN 204 after all the N11 messages from the SMFs 220are received. In such a scenario, the N2 Request message includes the N2SM information received in each of the N11 messages, and information toenable the AMF 218 to associate responses to the relevant SMF 220.

The (R)AN 204 may perform a RRC Connection Reconfiguration (6414)procedure with the UE 202 depending on the QoS information for all theQoS flows of the PDU sessions activated and the DRBs. The user planesecurity is established at this step. The (R)AN 204 forwards the MM NASService Accept to the UE 202. The UE 202 locally deletes the context ofthe PDU sessions that are not available in the 5G CN 206.

After the user plane radio resources are setup, the uplink data from theUE 202 may now be forwarded (6416) to the (R)AN 204. The 5G RAN 204sends the uplink data to the UPF 212 address and Tunnel ID provided insteps (6408) and (6410). The (R)AN 204 may send to the AMF 218 a N2Request ACK (6418) that includes the N2 SM information such as (R)ANTunnel information, the List of accepted QoS Flows for the PDU Sessionsactivated, and the List of rejected QoS Flows for the PDU Sessionsactivated). The message (6418) may include the N2 SM informationelement(s), e.g., RAN tunnel information. The (R)AN 204 may send the N2SM information with separate N2 messages, such as a N2 tunnel setupresponse, if the AMF 224 sends separate N2 messages in step (6412). Ifmultiple N2 SM information elements are included in the N2 Requestmessage (6412), the N2 Request ACK (6418) may include multiple N2 SMinformation elements, and information to enable the AMF 218 to associatethe responses to the relevant SMF 220. The AMF 218 may send to the SMF aN11 Message (6420) that includes the N2 SM information, such as RANTunnel information and the RAT Type, per accepted PDU Session to the SMF220. If the AMF 218 received the N2 SM information (one or multipleelements) in step (6418), then the AMF 218 forwards the N2 SMinformation to the relevant SMF 220. If the UE Time Zone has changed, ascompared to the last reported UE Time Zone, then the AMF 218 includesthe UE Time Zone IE in this message (6420). If dynamic PCC is deployed,the SMF 220 may optionally initiate an IP-CAN Session Modification(6422) and provides new location information to the PCF 222.

The SMF 220 may send to the UPF 212 a N4 Session Update Request (6424)message that includes RAN tunnel information. If a user plane is to besetup or modified, the SMF 220 initiates the N4 Session Modificationprocedure and provides the RAN Tunnel information. The UPF 212 may thensend to the SMF 220 a N4 Session Update Response (6426) message. The SMF220 may then send to the AMF a N11 Message ACK (6426) message.

A session state may be used to indicate that the UE 202 has activated aPDU session to send and receive data. Two types of session statesinclude an active state (sometimes named the “Session-ACTIVE” state) andan idle state (sometimes named the “Session-IDLE” state). The UE 202,the serving AMF 218, and the serving SMF 220 may locally maintain thesession state status.

When a PDU session is in the Session-IDLE state, the UP data connectionbetween the UE 202 and the UPF 212 terminating N3 tunnel is notestablished. The UE does not send or receive data in the Session-IDLEstate. The (R)AN 204 does not have PDU session context in theSession-IDLE state. The UPF 212 terminating N3 connection has the UE'sPDU session context, but without (R)AN N3 connection information (e.g.,no IP address of (R)AN 204 and no N3 tunnel endpoint identifier). TheSMF 220 may store the UE's PDU session context information relevant tothe SMF 220, but without (R)AN 204 information. The AMF 218 may storeall UE's PDU session context information relevant to the AMF 218.

When a PDU session is in the Session-ACTIVE state, the UE 202 may sendand receive data. The Uu interface between the UE 202 and (R)AN 204 isestablished in the Session-ACTIVE state. The N3 connection is beestablished when the PDU session is activated. The UE 202 has access toall PDU session context information, including DRB information. The AMF218 stores all UE's PDU session context information relevant to the AMF218. The SMF 220 stores all UE's PDU session context informationrelevant to the SMF 220.

Table 3 provides a description of the Session-ACTIVE and Session-IDLEstates for various network entities.

TABLE 3 Description of Session State Network Entity Session-ACTIVESession-IDLE UE 202 (maintains the Has all NAS and AS PDU session HasNAS and AS PDU Session State) context information session contextinformation without DRB information (R)AN 204 (does not maintain Has allPDU session context information. Has no PDU session context the SessionState) However, depending on the UE's data activity, the (R)AN 204 maynot have the UPF N3 connection information. UPF 212 (does not maintainHas all PDU session context information. Has PDU session context theSession State) However, depending on data activity, the without (R)AN N3UPF 212 may not have the (R)AN N3 connection information connectioninformation. AMF 218 (maintains the Has all PDU session contextinformation Has all PDU session context Session State and relevant toaccess and mobility information relevant to the N3 Connectionmanagement. access and mobility Status) management. SMF 220 (maintainsthe Has all PDU session context information. Has PDU session contextSession State and However, depending on the N3 Status without (R)ANinformation the N3 Connection Flag, the SMF 220 may not have (R)ANStatus) information if the N3 Connection Status is N3_DISCONNECTED.

FIG. 64 further illustrates, in a message flow diagram, an example of aUE-triggered Service Request procedure (6400) in the CM-IDLE state, inaccordance with embodiments of the present invention. The UE 202 maysend to the (R)AN 204 a MM NAS Service Request (6402) message thatincludes PDU session ID(s), security parameters, and a PDU sessionstatus. The UE 202 may send a NAS message Service Request (6402) towardsthe AMF 218 encapsulated in an RRC message to the RAN 204. The RRCmessage(s) that can be used to carry the 5G Temporary ID. If the ServiceRequest is triggered for user data, the UE 202 may include the PDUsession ID(s) in the NAS Service Request message (6402) to indicate thePDU session(s) that the UE 202 is requesting to use. If the ServiceRequest is triggered for signalling only, the UE 202 does not need toinclude any PDU session ID. When this procedure (6400) is triggered fora paging response, if the UE 202 needs to use some PDU session(s), theUE 202 may include those PDU session ID(s) in the MM NAS Service Requestmessage (6402). Otherwise the UE 202 does not need to include any PDUsession ID. The PDU session status indicates the PDU sessions availablein the UE 202.

The (R)AN 204 may then send to the AMF 218 a N2 Message (6404) thatincludes the MM NAS Service Request, a 5G Temporary ID, locationinformation, a RAT type, and a RRC establishment cause. If the AMF 218is not able to handle the Service Request, it will reject it. A 5GTemporary ID is obtained in a RRC procedure. The RAN 204 may selecs theAMF 218 according to this Temporary ID. The location information and theRAT type relates to the cell in which the UE 202 is camped. Based on thePDU session status, the AMF 218 may initiate the PDU session releaseprocedure if the PDU session is not available in the UE 202.

If the Service Request was not sent integrity-protected, or if integrityprotection is indicated as having failed, the AMF 218 may initiate a NASauthentication/security procedure (6406). If the UE 202 triggered theService Request to establish a signalling connection only, then afterthe security exchange, the UE 202 and the network can send signalling.

If the MM NAS Service Request message includes PDU session ID(s), or ifthis procedure (6400) is triggered by the SMF 220 but the PDU sessionIDs from the UE 202 correlates to other SMFs 220 than the one triggeringthe procedure, the AMF 218 sends a N11 message (6408) to SMF(s) 220associated with the PDU session ID(s). After receiving the N11 Message(6408), each SMF 220 sends a N11 Message (6410) to the AMF 218 toestablish the user plane(s) for the PDU sessions. The message (6410)includes N2 SM information such as a QoS profile, and CN N3 tunnelinformation). The N2 SM information includes information that the AMF220 may provide to the RAN 204.

The AMF 218 may send to the (R)AN 204 a N2 Request (6412) message thatincludes the N2 SM information received from the SMF 220, a securitycontext, an AMF Signalling Connection ID, a Handover Restriction List,and a MM NAS Service Accept. The RAN 204 may store the Security Context,AMF Signalling Connection Id, QoS Information for the QoS Flows of thePDU Sessions that are activated, and N3 Tunnel IDs in the UE RANcontext. The MM NAS Service Accept includes the PDU session status inthe AMF 218. The AMF 218 may include at least one N2 SM informationelement from the SMF 220 if the procedure (6400) is triggered for PDUsession user plane setup. The AMF 218 may send additional N2 SMinformation from the SMFs 220, if any, in separate N2 message(s), suchas a N2 tunnel setup request. Alternatively, if multiple SMFs 220 areinvolved, the AMF 218 may send one N2 Request message to the (R)AN 204after all the N11 messages from the SMFs 220 are received. In such ascenario, the N2 Request message includes the N2 SM information receivedin each of the N11 messages, and information to enable the AMF 218 toassociate responses to the relevant SMF 220.

The (R)AN 204 may perform a RRC Connection Reconfiguration (6414)procedure with the UE 202 depending on the QoS information for all theQoS flows of the PDU sessions activated and the DRBs. The user planesecurity is established at this step. The (R)AN 204 may forward the MMNAS Service Accept to the UE 202. The UE 202 may locally delete thecontext of the PDU sessions that are not available in the 5G CN 206. Ifthe (R)AN 204 accepts at least one of QoS flow, the UE 202 may store theactivated state of PDU session. Otherwise, the UE 202 considers theService Request as not accepted by the (R)AN 204.

After the user plane radio resources are setup, the uplink data from theUE 202 may now be forwarded (6416) to the (R)AN 204. The 5G RAN 204sends the uplink data to the UPF 212 address and Tunnel ID provided insteps (6408) and (6410). If the (R)AN 204 accepts at least one QoS flow,the message from the (R)AN 204 may send to the AMF 218 a N2 Request ACK(6418) that includes the N2 Reject ACK (including the PDU Session ID, N2SM information such as (R)AN Tunnel information, the List of acceptedQoS Flows for the PDU Sessions activated, and the List of rejected QoSFlows for the PDU Sessions activated). The message (6418) may includethe N2 SM information element(s), e.g., RAN tunnel information. The(R)AN 204 may send the N2 SM information with separate N2 messages, suchas a N2 tunnel setup response, if the AMF 224 sends separate N2 messagesin step (6412). If multiple N2 SM information elements are included inthe N2 Request message (6412), the N2 Request ACK (6418) may includemultiple N2 SM information elements, and information to enable the AMF218 to associate the responses to the relevant SMF 220. If the (R)AN 204does not accept the PDU session, the (R)AN 204 may send a N2 Request ACKmessage (6418) that indicates to the AMF 218 that the N2 SM Request isnot Accepted and a cause code. The message (6418) may include the PDUSession ID, the N2 SM information (including the PDU Session Reject, andthe cause code).

The AMF 218 may send to the SMF a N11 Message (6420) that includes thePDU Session ID, the N2 SM information such as RAN Tunnel information,and the RAT Type, per accepted PDU Session to the SMF 220. If the AMF218 received the N2 SM information (one or multiple elements) in step(6418), then the AMF 218 forwards the N2 SM information to the relevantSMF 220. If the UE Time Zone has changed, as compared to the lastreported UE Time Zone, then the AMF 218 includes the UE Time Zone IE inthis message (6420). If the PDU session is accepted, and if dynamic PCCis deployed, the SMF 220 may optionally initiate an IP-CAN SessionModification (6422) and provides new location information to the PCF222. The SMF 220 may send to the UPF 212 a N4 Session Update Request(6424) message that includes RAN tunnel information. If a user plane isto be setup or modified, the SMF 220 initiates the N4 SessionModification procedure and provides the RAN Tunnel information. The UPF212 may then send to the SMF 220 a N4 Session Update Response (6426)message. The SMF 220 may then send to the AMF a N11 Message ACK (6426)message. The message (6426) may include the PDU Session ID and the PDUsession state. The SMF 2225 may indicate the PDU session state(Activated or Deactivated) to the AMF 218.

A UE triggered Service Request in CM-CONNECTED state procedure may beused by a 5G UE 202 in the CM-CONNECTED state to request theestablishment of User Plane resources for the PDU sessions. The networkmay take further actions if the User Plane resource establishment is notsuccessful. It is noted that the procedure shown in FIG. 77 is notapplicable for an access network (once the UE 202 is registered in thenetwork) in which the UE 202 is always considered as in the CM-CONNECTEDstate, and in which the User Plane resource is always consideredestablished for an active PDU session.

FIG. 65 illustrates, in a message flow diagram, an example of a latepath switch procedure (6500) triggered by DL data without a UPF 212relocation, in accordance with embodiments of the present invention.This procedure (6500) may be used to trigger a path switch update whenthe DL data arrives at the UPF 212 and the UPF 212 does not have DLtunnel information. The UPF 212 receives downlink data packets (6502)from the DN 208. If the (R)AN N3 tunnel information is not available,the UPF 212 sends a N4 Message DL Data Notification (6504) message tothe SMF 220. The message (6504) includes a UE identifier (such as aSUPI) and a PDU Session ID. The SMF 220 sends a N4 Message DL DataNotification Acknowledgement (6506) message to the UPF 212.Alternatively, the acknowledgement (6506) may be performed by atransport network message protocol.

If the N3 Connection Status is currently set to N3_DISCONNECTED, the SMF220 sends a N11 Message (R)AN Information Request (6508) message to theAMF 218. The message (6508) includes a UE identifier (such as a SUPI), aPDU Session ID, and the N2 SM Message including the CN tunnelinformation (such as UPF Address and UPF N3 Tunnel Endpoint Identifier)for the (R)AN 204. The AMF 218 sends to the (R)AN a N2 Message PathSwitch Notification (6510) message that includes the PDU Session ID andthe N2 SM Message. The (R)AN 204 updates the CN tunnel information. The(R)AN 204 sends a N2 Message Path Switch Notification Acknowledgment(6512) message to the AMF 218. The message (6512) includes a PDU SessionID and (R)AN tunnel information such as the (R)AN Address and the TunnelEndpoint Identifier. The AMF 218 sends a N11 Message (R)AN InformationResponse (6514) message to the UPF 212. The message (6514) includes theUE identifier (such as a SUPI), the PDU Session ID, and the (R)AN tunnelinformation that includes the (R)AN type, the N3 (R)AN Address, and theN3 Tunnel Endpoint Identifier. The AMF 218 changes the N3 ConnectionStatus of the PDU session to N3 CONNECTED.

The SMF 220 sends a N4 Message Session Modification Request (6516)message to the UPF 212. The message (6516) includes the UE identifier(such as a SUPI), the PDU Session ID, and the (R)AN N3 tunnelinformation such as the (R)AN N3 Address and the downlink TunnelEndpoint Identifier. The UPF 212 updates the (R)AN tunnel informationfor the requested PDU session. The UPF 212 sends a N4 Message SessionModification Response (6518) to the SMF 220. The message (6518) includesa UE identifier and a PDU Session ID. The SMF 220 changes the N3Connection Status of the PDU session to N3_CONNECTED. The UPF 212 maysend downlink data packets to the UE 202 via the (R)AN 204 before orafter steps (6516) and (6518).

FIG. 66 illustrates, in a message flow diagram, an example of a latepath switch procedure (6600) triggered by UL data with UPF 212reselection, in accordance with embodiments of the present invention.This procedure (6600) may be used to trigger a path switch update whenthe UE 202 requests to send UL data. The UPF 212 may or may not bereselected. This procedure (6600) may be separated into two procedures:one for a late path switch triggered by uplink data as defined in FIG.57, and one for a UPF 212 relocation as defined in FIG. 68.

The UE 202 sends a UL Data Channel Grant Request message or a UL DataPacket (6602) to the (R)AN 204 for a PDU session. If the UPF N3 tunnelinformation is not available in the (R)AN 204, the (R)AN 204 sends theN2 Message Session Path Switch Request (6604) message to the AMF 218.The message (6604) includes the PDU Session ID and the (R)AN tunnelinformation, such as the (R)AN Address and the (R)AN N3 Tunnel EndpointIdentifier. The AMF then sends a N11 Message Session Path Switch Request(6606) message to the SMF 220, including the UE identifier (such as aSUPI), the PDU Session ID, and the (R)AN tunnel information such as the(R)AN type, the N3 (R)AN Address and the downlink Tunnel EndpointIdentifier.

The SMF 220 selects the target UPF 212 t to serve the PDU session basedon criteria in Clause 6.3.3 of TS 23.502 (6608). The SMF 220 assigns theN3 tunnel information, such as the N3 uplink Tunnel Endpoint Identifier.The SMF 220 sends a N4 Message Session Establishment Request (6610)message to the target UPF 212 t. The message (6610) includes the PDUSession ID, the QoS policy, the charging policy, and (R)AN tunnelinformation. The (R)AN tunnel information may include the (R)AN Address,the downlink tunnel endpoint identifier, and the N3 and N9 downlinktunnel information such as the Anchor UPF Address and the N9 downlinkTunnel Endpoint Identifier. The target UPF 212 t updates the (R)ANtunnel information and anchor UPF 212 a tunnel information. The targetUPF 212 t sends a N4 Message Session Establishment Response (6612)message to the SMF 220. The message (6612) includes the UE identifier(such as a SUPI) and the PDU Session ID.

The SMF 220 sends a N4 Message Session Modification Request (6614)message to the anchor UPF 212 a (such as the session anchor UPF). Themessage (6614) includes the UE identifier (such as a SUPI), and the N9Target UPF tunnel information such as the target UPF Address and the N9uplink Tunnel Endpoint Identifier. The anchor UPF 212 a updates thetarget UPF tunnel information. The anchor UPF 212 a sends a N4 MessageSession Modification Response (6616) message to the SMF 220. The SMF 220sends a N11 Message Session Path Switch Response (6618) message to theAMF 218. The message (6618) includes the UE identifier (such as a SUPI),the PDU Session ID, and the N2 SM Message that includes the N3 CN TunnelInformation for the (R)AN 204. The SMF 220 changes the N3 ConnectionStatus of the PDU session to N3_CONNECTED. The SMF 220 starts a timer,to be used in step (6624).

The AMF 218 sends a N2 Message Session Path Switch Response (6620)message to the (R)AN 204 that indicates that the path switch iscompleted. The message (6620) includes the PDU Session ID, and the N2 SMMessage received from the SMF 220. The AMF 218 changes the N3 ConnectionStatus of the PDU session to N3_CONNECTED. The (R)AN 204 updates the CNtunnel information and sends uplink data packets (6622). Once the timerset in step (6618) expires, the SMF 220 sends a N4 Message SessionTermination Request (6624) message to the source UPF 212 s. The message(6624) includes the UE identifier (such as a SUPI) and the PDU SessionID. The source UPF 212 s deletes the PDU session context. The source UPF212 s sends a N4 Message Session Termination Response (6626) to the SMF220.

FIG. 67 illustrates, in a message flow diagram, an example of a latepath switch procedure (6700) triggered by DL data with UPF 212reselection, in accordance with embodiments of the present invention.This procedure (6700) may be used for a late path switch triggered by DLdata arriving at the UPF 212. First the CN performs a path switchprocedure without UPF 212 reselection. After that, if the SMF 220determines that the UPF 212 needs to be relocated, the SMF 220 performsthe UPF 212 reselection procedure.

The anchor UPF 212 a for the PDU session sends downlink data packets(6702) to the source UPF 212 s. Next, steps (6504) to (6520) of the latepath switch procedure (6500) triggered by DL data without UPF 212reselection is performed. The SMF 212 selects a new UPF 212 (6704). If anew UPF 212 is selected (6704), a UPF 212 reselection procedure (6800)is performed.

FIG. 68 illustrates, in a message flow diagram, an example of a UPF 212reselection procedure (6800), in accordance with embodiments of thepresent invention. This procedure (6800) may be used to establish a newUPF 212 that terminates the N3 connection. The SMF 220 selects thetarget UPF 212 t to serve the PDU session based on criteria in Clause6.3.3 of TS 23.502. The SMF 220 assigns N3 tunnel information (such asthe N3 uplink Tunnel Endpoint Identifier), and the N9 tunnel information(such as the N9 Anchor UPF Address and the N9 uplink Tunnel EndpointIdentifier). The SMF 220 sends a N4 Message Session EstablishmentRequest (6802) message to the target UPF 212 t. The message (6802)includes the PDU Session ID, the QoS policy, the charging policy, andthe (R)AN tunnel information such as the (R)AN Address, the downlinkTunnel Endpoint Identifier, and the N3 and N9 tunnel information. Thetarget UPF 212 t updates the (R)AN, N3, and N9 tunnel information. Thetarget UPF 212 t sends a N4 Message Session Establishment Response(6804) message to the SMF 220. The message (6804) includes the UEidentifier (such as a SUPI) and the PDU Session ID.

The SMF 220 sends a N4 Message Session Modification Request (6806)message to the anchor UPF 212 a (such as the Session Anchor UPF). Themessage (6806) includes the UE identifier (such as a SUPI), and the N9Target UPF tunnel information such as the Target UPF Address and the N9downlink Tunnel Endpoint Identifier. The anchor UPF 212 a updates thetarget UPF 212 t tunnel information. The anchor UPF 212 a sends a N4Message Session Modification Response (6808) message to the SMF 220. Theanchor UPF 212 a can send downlink data (6810) to the UE 202 via thetarget UPF 212 t. The SMF 220 sends a N2 SM Message Session ModificationRequest (6812) message to the (R)AN 204 by using a message transferservice of the AMF 218. The message (6812) to the AMF 218 includes theUE identifier (such as a SUPI), and the N2 SM Message SessionModification Request message to the (R)AN 204 that includes the PDUSession ID, and the N3 tunnel information (such as the UPF Address andthe Tunnel Endpoint Identifier. The (R)AN 204 stores the N3 tunnelinformation and sends a N2 SM Message Session Modification Response(6814) message to the SMF 220 via the AMF 218. The message (6814)includes the PDU Session ID. The AMF 218 adds the UE identifier (such asa SUPI) and forwards the N2 SM Message Session Modification Responsemessage to the SMF 220. The UE 202 and (R)AN 204 may send UL data (6816)to the target UPF 212 t and the anchor UPF 212 a. The SMF 220 sends a N4Message Session Termination Request (6818) message to the source UPF 212s. The source UPF 212 s sends a N4 Message Session Termination Response(6820) message to the SMF 220.

If a N2 UE Context Release Request is performed immediately after theSMF 220 deactivates the PDU session, the (R)AN 204 can release N3interface and radio interface (including Uu) information before the UPF212 receives instruction from the SMF 220 to start buffering downlinkpackets. It is thus possible that the UPF 212 can forward some downlinkpackets to the (R)AN 204 where the (R)AN 204 has no UE contextinformation. Hence, the (R)AN 204 may drop those packets which may leadto important information being lost when the packets are dropped, and/orincorrect billing since the UPF 212 is not aware that the packets weredropped. To avoid this situation, the AMF 218 may collect all theresponses from SMF(s) 220 confirming session deactivation was completebefore requesting the (R)AN 204 to release the UE context.

FIG. 69 illustrates, in a message flow diagram, an example of aprocedure for a UE context release in an AN (6900), in accordance withembodiments of the present invention. This procedure (6900) may be usedto release the logical N2-AP (Application Protocol) signallingconnection and the associated N3 User Plane connections. When the N2-APsignalling connection is lost due to (R)AN 204 or AMF 218 failure, theUE context release in the AN procedure (6900) may be performed locallyby the AMF 218 or the (R)AN 204 as described in the procedure flow belowwithout using or relying on any of the signalling shown between (R)AN204 and AMF 218. The UE context release in the AN procedure (700) mayresult in all PDU sessions of the UE 202 to be deactivated.

The initiation of UE context release in the AN procedure (6900) may be(R)AN-initiated with a cause, e.g., O&M Intervention, UnspecifiedFailure, AN (e.g., Radio) Link Failure, User Inactivity, Release due toUE generated signalling connection release (6902 a), etc. The initiationof the procedure (6900) may also be AMF-initiated (6902 b) with a cause,e.g. Unspecified Failure, etc. Both the (R)AN-initiated and theAMF-initiated steps of the UE context release in the AN procedure (6900)are shown in FIG. 69.

If there are confirmed AN conditions (e.g., Radio Link Failure) or forother (R)AN 204 internal reasons, the (R)AN 204 may initiate the UEcontext release in the AN procedure (6900). In this case, the (R)AN 204sends a N2 UE Context Release Request message (6902 b) to the AMF 218.The message may include a Cause (or a cause code) that indicates (orrepresents) the reason for the release (e.g., AN Link Failure, O&Mintervention, unspecified failure, etc.). The initiation of a UE contextrelease in the AN procedure (6900) may also be triggered by an internalAMF 218 event.

The AMF 218 may send one message to each SMF 220 serving multipleactivated PDU sessions to request deactivation of these PDU sessions.For each of the SMF serving activated PDU sessions, the AMF 218 mayrequest the SMF 220 to deactivate the PDU sessions: the AMF 218 may senda N11 PDU session deactivation Request message (6904) to the SMF 220.The message (6904) may include an UE identifier (such as SUPI), a (R)ANidentifier (such as (R)AN Address), and a Release Cause (or cause code).The AMF 218 may also store the deactivated state of the PDU session. Itis noted that this step (6904) could also be via a service of AMF:Namf_UE Mobility Event Notification (SMF). In this case, the AMF 218 maysend (via a N11 message) a UE Mobility Event Notification, whichindicates the N2 Release event, to the SMF(s) 220 that serve active PDUsession(s) of the UE 202 as defined in Clause 5.2.2.2 of TS 23.502. Themessage may include the a UE identifier (such as SUPI), the (R)ANidentifier information (such as (R)AN address), and the cause code. The(R)AN identifier information may be used to distinguish between multiple(R)ANs in the case where a UE is connected to multiple (R)ANs.

Next, the SMF 220 may send to the UPF 212 a N4 Session ModificationRequest message (6906 a). This message (6906 a) may include the ANtunnel information to be removed. Thus, the SMF initiates a N4 SessionModification procedure (6906 a) indicating the need to remove AN TunnelInformation. A buffering command may indicate whether the UPF 212 is tobuffer an incoming DL PDU. It is noted that the request (6906 a)includes a “Buffering command”, then the UPF 212 may start bufferingdownlink PDUs received for the UE 202, and initiate the “NetworkTriggered Service Request” procedure, described in clause 4.2.3.3 of TS23.502, if downlink PDU arrives for the PDU session. Next, the UPF 212may send to the SMF 220 a N4 Session Modification Response message (6906b) acknowledging the SMF 220 request. The SMF 220 may store thedeactivated state of PDU session.

Next, the SMF 220 may send to the AMF 218 a N11 PDU session deactivationResponse message (6908). It is noted that this step (6908) could also beimplemented by using a service of SMF: Nsmf_PDU Session Event ReportNotification (AMF). The SMF 220 may send (via a N11 message) a PDUSession Event Report Notification as defined in Clause 5.2.8.1 of TS23.502. The notification may include a UE Identifier (such as a SUPI),PDU Session ID(s), and an event trigger (such as the deletion of (R)ANtunnel information). After the AMF 218 collects all the PDU sessiondeactivation Response in step (6908) from the SMF(s) 220 that werenotified in Step (6904), the AMF 218 may send to the (R)AN 204 a N2 UEContext Release Request message (6910).

If the AN connection (e.g., a RRC connection) with the UE 202 is notalready released (step 6902 a), the (R)AN 204 requests the UE 202 torelease the AN connection (6912). Upon receiving an AN connectionrelease confirmation from the UE 202, the (R)AN 204 may delete the UE'scontext. The (R)AN 204 may confirm the N2 Release by returning an N2 UEContext Release Complete ( ) message (6914) to the AMF 218. With this,the signalling connection between the AMF 218 and the (R)AN 204 for thatUE 202 is released. It is noted that, during this procedure, the AN mayprovide location information to the AMF 218.

A PDU session release procedure may be used to release all resourcesassociated with a PDU session. Such resources may include the IPaddress/Prefixes allocated for an IP-based PDU session, which mayinclude the release of multiple Prefixes in case of Multi-homing (asdefined in TS 23.501). Such resources may also include any UPF 212resource (including N3/N9 termination) that was used by the PDU session.The SMF 220 may notify any entity associated with the PDU session of aPDU session release. Such entities include the PCF 222, and the DN 208(e.g., when DN 208 authorization has taken place during the PDU sessionestablishment).

In some implementations, for deactivated PDU sessions, the SMF 220 maysend an Asynchronous Session Release (ASR) Flag and the PDU Session IDto inform the AMF 218 about a session release request and to indicatewhether or not the PDU session release procedure can be asynchronouslyperformed. If the ASR Flag is set to FALSE, the PDU session may berelease immediately, regardless of the CM state of the UE 202. If theASR Flag is set to TRUE, the PDU session release can be performed whenthe UE 202 is in CM-CONNECTED state. The ASR Flag and PDU Session ID inthe message from the SMF 220 to the AMF 218 may be included according tothe following:

-   -   For an activated PDU session, if the UE 202 is in a CM-CONNECTED        state, the PDU session may be released immediately. Hence, the        SMF 220 does not need to send an ASR Indication to the AMF 218.    -   For a deactivated PDU session, the SMF 220 may send the ASR Flag        and PDU Session ID in the message to the AMF 218. If the ASR        Flag is set to FALSE, the AMF 218 may send N1 SM Information        (PDU Session Release Request) to the UE 202 immediately. If the        UE 202 is in the CM-IDLE state, the AMF 218 may page the UE 202        to enter the CM-CONNECTED state. If the UE 202 receives the        paging, the AMF 218 may send to the UE 202 the N1 SM Information        (PDU Session Release Request). If the UE 202 cannot receive the        paging, the AMF 218 may send an “undelivered error message” to        the SMF 220, indicating the cause code (e.g., UE Unreachable).        The SMF 220 and AMF 218 may then release the PDU session. The        session status in the AMF 218 and UE 202 may be synchronized        when the UE 202 performs a Service Request or Registration        procedures. If the ASR Flag is set to TRUE, the PDU session in        the UE 202 may be released if the UE 202 is in the CM-CONNECTED        state. If the UE 202 is in the CM-IDLE state, the PDU session        status in the UE 202 and CN 206 may be synchronized when the UE        202 performs Service Request or Registration procedures.

FIG. 70 illustrates, in a message flow diagram, an example of aprocedure for a UE 202 or CN 206 requested PDU session release forNon-Roaming and Roaming with Local Breakout (7000), in accordance withembodiments of the present invention. FIG. 70 illustrates both the UErequested PDU session release procedure and the network requested PDUsession release procedure. The procedure (7000) allows the UE 202 torequest the release of one PDU session. The procedure (7000) also allowsthe SMF 220 or PCF 222 to initiate the release of a PDU session. In thecase of Local BreakOut (LBO), the procedure (7000) is as in the case ofnon-roaming with the difference that the SMF 220, the UPF 212 and thePCF 222 are located in a visited network.

The procedure (7000) may be triggered by the UE 202, the PCF 222 or bythe SMF 220. The UE 202 may initiate the procedure (7000) via atransmission of a N1 SM PDU Session Release Request message (7002 a) tothe SMF 220. The message (7002 a) may include the PDU Session ID, andmay be relayed by (R)AN 204 to the AMF 218 corresponding to the PDUSession ID over N2 interface and the relayed by the AMF 218 over N11interface to the SMF 220. Depending on the access type, when the UE 202is in a CM-IDLE state, the UE 202 can trigger a Service Requestprocedure before being able to release the PDU session. The PCF mayinitiate the procedure (7000) by initiating a PDU-CAN Sessionmodification procedure (7002 b) to request the release of the PDUsession. The SMF 220 may initiate the procedure (7000) by releasing aPDU session (7002 c), for example, based on a request from the DN 208(e.g., cancelling the UE 202 authorization to access to the DN 208), orbased on a request from the UDM (e.g., a subscription change) or fromthe Online Charging System (OCS). The release procedure (7002 c) alsomay be triggered based on locally configured policy. For example, therelease procedure (7002 c) may be related with the UPF 212 relocationfor service and session continuity (SSC) mode 2/mode 3. If the SMF 220receives one of the triggers in step (7002 a) to (7002 c), the SMF 220may start the PDU session release procedure (7000).

The SMF 220 may release the IP address/Prefix(es) that were allocated tothe PDU session, and may also releases the corresponding User Planeresources. The SMF 220 may send an N4 Session Release Request message(7004 a) to the UPF 212. The message (7004) may include the N4 SessionID. The UPF 212 may drop any remaining packets of the PDU session andrelease all tunnel resource and contexts associated with the N4 Session.The UPF 212 may acknowledge the N4 Session Release Request by thetransmission of an N4 Session Release Response message (7004 b) to theSMF 220. The message (7004 b) may include the N4 Session ID. If thereare multiple UPFs 212 associated with the PDU session, steps (7004 a)and (7004 b) may be performed for each UPF 212. If Dynamic PCC appliedto this session, the SMF 220 may initiate the PDU-CAN sessiontermination procedure (7006). If it is the last PDU session that the SMF220 is handling for the UE 202, the SMF 220 may release the associationwith the UDM.

The SMF 220 may send an N11 Request message (7008) to the AMF 218. Themessage (7008) may include the N2 SM Resource Release request, and N1 SMInformation such as the PDU Session Release Command. The SMF 220 maycreate the N1 SM Information including the PDU Session Release Commandmessage that includes the PDU Session ID, and a Cause (or a cause code).The Cause may indicate a trigger to establish a new PDU session with thesame characteristics (e.g., when procedures related with SSC mode 2 areinvoked). It is noted that SSC mode 2 is defined in TS 23.502 clause5.6.9.

In some implementations, an asynchronous communication type “ACM”Indication is used as described below. If the UP connection of the PDUsession is active, the SMF 220 may also create an N2 SM request torelease the (R)AN 204 resources associated with the PDU session. This N2SM request may include a N2 Resource Release request that includes thePDU Session ID. The SMF 220 may send an N11 message (7008) to the AMF218. The message (7008) may include the N2 SM Resource Release request,and a N1 SM Container that includes the PDU Session Release Command. Ifthe PDU session is deactivated, the “ACM” Indication indicates to theAMF 218 whether it may skip sending the N1 SM container to the UE 202(e.g., when the UE 202 is in CM-IDLE mode). If the UE 202 is in CM-IDLEstate, and the “ACM” Indication is included in the N11 message, steps(7010) to (7014) may be skipped. Otherwise, if the UE 202 is in CM-IDLEstate and “ACM” is not indicated, the AMF 218 may initiate the networktriggered Service Request procedure to transmit the N1 SM Information tothe UE 202. If the UE 202 is in the CM-CONNECTED state, then the AMF 218may transfer the message received from the SMF 218 in step (7008) to the(R)AN 204. This may be performed by sending a N2 SM Resource Releaserequest message (7010) to the (R)AN 204, where the message (7010) mayinclude N1 SM Information. It should be noted that the UE 202 and the 5GCore (e.g., CN 206) will get synchronized with respect to the status(e.g., released) of the PDU session at the next Service Request orRegistration procedure. When the (R)AN 204 has received an N2 SM request(7010) to release the AN resources associated with the PDU session, the(R)AN 204 issues AN specific signalling exchange(s) (7012) with the UE202 to release the corresponding AN resources. In case of a 3GPP RAN, anRRC Connection Reconfiguration may take place with the UE 202 releasingthe (R)AN 204 resources related to the PDU session. During thisprocedure, the (R)AN 204 may send any NAS message (such as a N1 SM PDUSession Release Command) received from the AMF 218 in step (7010). TheUE 202 may acknowledge the PDU Session Release Command by sending a PDUSession Release ACK message (7012) via N1 SM signalling sent over the(R)AN 204. If the (R)AN 204 had received a N2 SM request to release theAN resources (7010), the (R)AN 204 may acknowledge the N2 SM ResourceRelease Request by sending an N2 SM Resource Release ACK message (7014)to the AMF 218. The message (7014) may include the N1 SM Informationthat includes the PDU Session Release Ack. Otherwise, the (R)AN 204 mayforward the N1 SM Information that includes the PDU Session Release ACKfrom the UE 202 to the AMF 218. If the UE 202 is in a CM-CONNECTEDstate, the AMF 218 may send a N11 Response message (7018) to the SMF220. The message (7018) may include the N1 SM Information that includesthe PDU Session Release Ack. Otherwise, if the UE 202 is in the CM-IDLEstate, the AMF 218 may notify the SMF 220 of the undelivered N1 SMmessage with a cause code indicating the N2 has been released or the UE202 is in the CM-IDLE state.

In other implementations, an Asynchronous Session Release (ASR) Flagtogether with PDU Session ID are used, as described below. If the UPconnection of the PDU session is active, the SMF 220 may also create anN2 SM request to release the (R)AN 204 resources associated with the PDUsession. This N2 SM request may include a (R)AN Resource Release requestthat includes the PDU Session ID. The SMF 220 may send an N11 message(7008) to the AMF 218. The message (7008) may include the N2 SM ResourceRelease request, and the N1 SM Container (that includes the PDU SessionRelease Command). The N11 message (7008) may further include the ASRFlag and the PDU Session ID. The ASR Flag may provide an indication tothe AMF 218 about the session release notification and whether it mayskip sending the N1 SM container to the UE 202 (e.g., when the UE 202 isin the CM-IDE mode). If the UE 202 is in CM-IDLE state, and an ASM Flagset to TRUE is included in the N11 message, the AMF acknowledges thatsteps (7010) to (7014) may be skipped. Otherwise, if the UE 202 is inCM-IDLE state and the ASR Flag is set to FALSE, the AMF 218 may initiatethe network triggered Service Request procedure to transmit the N1 SMInformation to the UE 202. If the UE 202 receives the paging, the AMF218 may send to the UE 202 the N1 SM Information (including the PDUSession Release Request). The paging message may also carry the N1 SMInformation (including the PDU Session Release Request). If the UEcannot receive paging, the AMF 218 may send to the SMF 220 an“undelivered error message” with a cause indicating that the UE isunreachable in step (7018). If the UE 202 is in the CM-CONNECTED state,then the AMF 218 may transfer the message received from the SMF 218 instep (7008) to the (R)AN 204. This may be performed by sending a N2 SMResource Release request message (7010) to the (R)AN 204, where themessage (7010) may include N1 SM Information. It should be noted thatthe UE 202 and the 5G Core (e.g., CN 206) will get synchronized withrespect to the status (e.g., released) of the PDU session at the nextService Request or Registration procedure. When the (R)AN 204 hasreceived an N2 SM request (7010) to release the AN resources associatedwith the PDU session, the (R)AN 204 issues AN specific signallingexchange(s) (7012) with the UE 202 to release the corresponding ANresources. In case of a 3GPP RAN, an RRC Connection Reconfiguration maytake place with the UE 202 releasing the (R)AN 204 resources related tothe PDU session. During this procedure, the (R)AN 204 may send any NASmessage (such as a N1 SM PDU Session Release Command) received from theAMF 218 in step (7010). The UE 202 may acknowledge the PDU SessionRelease Command by sending a PDU Session Release ACK message (7012) viaN1 SM signalling sent over the (R)AN 204. If the (R)AN 204 has receiveda N2 SM request to release the AN resources (7010), the (R)AN 204 mayacknowledge the N2 SM Resource Release Request by sending an N2 SMResource Release ACK message (7014) to the AMF 218. The message (7014)may include the N1 SM Information that includes the PDU Session ReleaseAck. Otherwise, the (R)AN 204 may forward the N1 SM Information thatincludes the PDU Session Release ACK from the UE 202 to the AMF 218. Ifthe UE 202 is in the CM-IDLE state and the ASR Flag is set to TRUE instep (7008208), the AMF 218 may acknowledge the SMF 220 message (7008)and step (7018) is skipped. The SMF 220 and the AMF 218 may release thePDU session. The PDU session status in the AMF 218 and the UE 202 may besynchronized when the Service Request or Registration procedures areperformed. If the UE 202 is in the CM-IDLE state and the ASR Flag is setto FALSE in step (7008), the AMF 218 may fail to page the UE 202 and theAMF may send an “undelivered error” message that includes the PDUSession Release Indication, the PDU Session ID and the cause code (e.g.,UE Unreachable). Step (7018) is skipped. The SMF 220 and the AMF 218 mayrelease the PDU session. The session status in the AMF 218 and the UE202 may be synchronized when the UE 202 performs a Service Request orRegistration procedures. Otherwise, the AMF 218 may send an N11 Responsemessage to the SMF 220, with the message including the N1 SM Information(such as the PDU Session Release ACK).

In yet other implementations using a Session Release Indication is usedas described below. If the PDU session is deactivated, the SMF 220 maysend a Session Release indication and PDU Session ID to the AMF 218. TheSMF 220 may send an N11 message (7008) to the AMF 218. The message(7008) includes the N2 SM Resource Release request, the N1 SM Container(including the PDU Session Release Command), the PDU Session ReleaseIndication, and the PDU Session ID. The N2 SM Resource Release requestmessage may include N1 SM Container. The PDU Session Release Indicationindicates to the AMF 218 about the PDU session release notification. Ifthe PDU session is deactivated, the SMF shall may the PDU SessionRelease Indication and PDU Session ID in message 7008. The AMF 218 mayskip sending the N1 SM container to the UE 202 when the UE 202 is in theCM-IDLE state. If the UE 202 is in the CM-IDLE state, the AMF 218 mayacknowledge step (7008) in step (7018), and steps (7010) to (7014) and(7018) are skipped. The AMF 218 may release all PDU session contexts. Itis noted that the UE 202 and the 5G Core, such as AMF 218, 206 will getsynchronized about the status (e.g., released) of the PDU session at thenext Service Request or Registration procedure. If the UE 202 is in theCM-CONNECTED state, the PDU Session Release Indication and PDU SessionID are not included in the message in step (7008), then the AMF 218 maytransfer the message received from the SMF 220 in step (7008). If the(R)AN 204 receives an N2 SM Resource Release request message (7010) torelease the AN resources associated with the PDU session, it may issueAN specific signalling exchange(s) (7012) with the UE 202 to release thecorresponding AN resources. In case of a 3GPP RAN, an RRC ConnectionReconfiguration may take place with the UE 202 releasing the (R)AN 204resources related to the PDU session. During this procedure (7000), the(R)AN 204 may send any NAS message (e.g., N1 SM PDU Session ReleaseCommand) received from the AMF 218 in step (7010). If the (R)AN 204receives only the N1 SM Container (including the PDU Session ReleaseCommand), the (R)AN 204 may forward this message to the UE 202. The UE202 acknowledges the PDU Session Release Command by sending a PDUSession Release ACK message via N1 SM signalling sent over the (R)AN204. If the (R)AN 204 has received an N2 SM request to release the ANresources, the (R)AN 204 may acknowledge the N2 SM Resource ReleaseRequest by sending an N2 SM Resource Release ACK (including the N1 SMInformation including the PDU Session Release ACK) message (7014) to theAMF 218. Otherwise, the (R)AN 204 may forward the N1 SM Information(including the PDU Session Release ACK) from the UE 202 to the AMF 218.If the UE 202 is in the CM-CONNECTED state, the AMF 218 may send the N11message (7018) to forward messages received from (R)AN 204 in step(7014) to the SMF 220. If the UE 202 is in the CM-IDLE state, the AMF218 may send to the SMF 220 an N11 message (including the SessionRelease Acknowledgment, and an identifier for the PDU session such asPDU Session ID). The SMF 220 may release all PDU session contexts andstep (7018) is skipped.

The SMF 220 may notify the AMF 218 that the PDU session is released viaa N11 message (7018). The AMF 218 and SMF 220 may remove all contexts(including the PDU session ID) associated with the PDU session. Anexample for step (7018) may be the SMF 220 sending to the AMF 218, via aN11 Message, a PDU Session Event Report Notification as defined inClause 5.2.8.1 of TS 23.502. In this example, the event trigger is a PDUsession release. It should be noted that, in some embodiments, the orderwith which the SMF 220 releases the resources may be implementationdependant.

In another example of the PDU Session Release procedure (7000), the SMF220 knows the UE connection management (CM) state (e.g., CM-IDLE orCM-CONNECTED). The SMF 220 serving the PDU session subscribes to the UEmobility event notification service of the AMF 218. When the UE changesthe CM state, the AMF 218 may notify the SMF 220.

If the PDU session is activated, in step (7008), the SMF 220 sends anN11 Request message to the AMF 218. The message includes the N2 SMResource Release request, and N1 SM Information (including the PDUSession Release Command). The SMF 220 creates an N1 SM Informationincluding the PDU Session Release Command message (that includes the PDUSession ID and the Cause). The Cause may indicate a trigger to establisha new PDU session with the same characteristics (e.g., when proceduresrelated with SSC mode 2 are invoked).

If the PDU session is deactivated (deactivated UP) and the UE 202 is inthe CM-IDLE state, in step (7008), the SMF 220 sends an N11 Requestmessage to the AMF 218. The message includes the PDU Session ReleaseIndication and the PDU Session ID.

In step (7010), if the UE 202 is in the CM-CONNECTED state, the AMF 218forwards the message received in step (7008) to the (R)AN 204 via the N2interface. If the UE 202 is in the CM-IDLE state, steps (7010) to (7012)and (7018) are skipped. The AMF 218 releases all the PDU sessioncontexts locally. The PDU session status in the UE 202 and in the 5GCore network (such as AMF 218) are synchronized in the next ServiceRequest or Registration procedure.

In step (7012), if the (R)AN 204 receives an N2 SM request to releasethe (R)AN resources associated with the PDU session, it issues (R)ANspecific signalling exchange(s) with the UE 202 to release thecorresponding (R)AN resources. In case of a 3GPP (R)AN 204, an RRCConnection Reconfiguration may take place with the UE 202 releasing the(R)AN 204 resources related to the PDU session. During this procedure,the (R)AN 204 sends any NAS message (e.g., N1 SM PDU Session ReleaseCommand) received from the AMF 218 in step (7010).

In step (7012), if the (R)AN 204 receives an N1 SM Information only, the(R)AN 204 forwards this message to the UE 202. The UE 202 acknowledgesthe PDU Session Release Command by sending a PDU Session Release Ackmessage via N1 SM signalling sent over the (R)AN 204.

In step (7014), if the (R)AN 204 has received a N2 SM request to releasethe (R)AN resources in step (7010), the (R)AN 204 acknowledges the N2 SMResource Release Request by sending an N2 SM Resource Release Ack(including the N1 SM Information (PDU Session Release Ack) Message tothe AMF 218. Otherwise, if the (R)AN 204 has received only an N1 SMinformation in step (7010), the (R)AN 204 may forward the N1 SMInformation (PDU Session Release Ack) from the UE 202 to the AMF 218.

In step (7018), if the UE 202 is in the CM-CONNECTED state, the AMF 218sends the N11 Response message to forward the message received from(R)AN 204 in step (7014), which includes the N1 SM Information(including the PDU Session Release Ack), to the SMF 220.

In step (7018), if the UE 202 is in the CM-IDLE state, the AMF 218 sendsthe N11 message (including the PDU Session Release Acknowledgment, andthe PDU Session ID) to the SMF 220 in response to the SMF 220 message instep (7008). Step (7018) is skipped. The SMF 220 releases all PDUSession Contexts of the released PDU session.

In Step (7018), the SMF 220 notifies the AMF 218 that the PDU session isreleased. The AMF 218 and SMF 220 may remove all contexts (including thePDU session ID) associated with the PDU session.

FIG. 71 illustrates, in a message flow diagram, an example of aprocedure for a UE 202 or CN 206 requested PDU session release forHome-routed Roaming (7100), in accordance with embodiments of thepresent invention. This procedure (7100) is used in case of home-routedroaming scenarios. Some of the steps in the PDU session release forHome-routed Roaming procedure (7100) are similar to steps in the PDUsession release for Non-Roaming and Roaming with Local Breakoutprocedure (7000).

The PDU session release for Home-routed Roaming procedure (7100) may betriggered by the UE 202, the PCF 222 or by the SMF in the HPLMN (H-SMF)220 h. The UE 202 may initiate the procedure (7100) via a transmissionof a SM PDU Session Release Request message (7102) to the AMF 220. Themessage (7102) may include the PDU Session ID, and may be relayed (7104)to the SMF in the VPLMN (V-SMF) 220 v corresponding to the PDU SessionID via N11 and the AMF 218. The V-SMF 220 v then may send a Release PDUSession Request message (7106) Depending on the access type, when the UE202 is in a CM-IDLE state, the UE 202 can trigger a Service Requestprocedure before being able to release the PDU session. The PCF 222 mayinitiate the procedure (7100) by initiating a PDU-CAN Sessionmodification procedure (7108) to request the release of the PDU session.The H-SMF 220 h may initiate the procedure (7100) by releasing a PDUsession (7110), as described above in step (7002 c) of FIG. 70. If theH-SMF 220 receives one of the triggers in steps (7106) to (7110), theH-SMF 220 may start the PDU session release procedure (7100).

The H-SMF 220 may release the IP address/Prefix(es) that were allocatedto the PDU session, and may also release the corresponding User Planeresources. The H-SMF 220 may send an N4 Session Release Request message(7112 a) to the UPF 212. The message (7112 a) may include the N4 SessionID. The UPF 212 may drop any remaining packets of the PDU session andrelease all tunnel resource and contexts associated with the N4 Session.The UPF 212 may acknowledge the N4 Session Release Request by thetransmission of an N4 Session Release Response message (7112 b) to theH-SMF 220. The message (7112 b) may include the N4 Session ID. If thereare multiple UPFs 212 associated with the PDU session, steps (7112 a)and (7112 b) may be performed for each UPF 212. If Dynamic PCC appliedto this session, the H-SMF 220 may initiate the PDU-CAN sessiontermination procedure (7114). If it is the last PDU session that theH-SMF 220 is handling for the UE 202, the H-SMF 220 may release theassociation with the UDM.

Next, the H-SMF 220 h may send a Release PDU Session Command message(7116) to the V-SMF 220 v. This message (7116) may include theSubscriber Permanent Identity, the PDU Session ID, and the NAS message.Next, the V-SMF 220 v may release the corresponding User Plane resourcesusing steps (7118 a) and (7118 b). This may include the same procedureas in steps (7112 a) and (7112 b), but controlled from the SMF in theVPLMN (V-SMF 220 v). Steps (7120) to (7130) are similar to (7008) to(7018) as described above with reference to FIG. 70, with the SMF beingthe H-SMF 220 h. Next, the V-SMF 220 v may send a Release PDU SessionConfirm message (7132) to the H-SMF 220 h. The message (7132) mayinclude the Subscriber Permanent Identity, and the PDU Session ID. TheH-SMF 220 h may remove all contexts associated with the PDU session.

FIG. 72 illustrates, in a message flow diagram, an example of a Xn basedinter NG (R)AN handover procedure (7200) without user plane functionrelocation, in accordance with embodiments of the present invention.This procedure (7200) may be used to hand over a UE 202 from a source(R)AN 204 to target (R)AN 204 t using Xn interface when the AMF 218 isunchanged and the SMF 220 decides to keep the existing UPF 212 (e.g.,the UPF 212 which terminates the N3 interface in the NG Core Network(NGC). The presence of IP connectivity between the source UPF 212 andtarget UPF 212 is assumed.

The procedure (7200) includes handover preparation (7202) and handoverexecution (7204). The handover execution (7204) includes the forwardingof data (7206) from a source (R)AN 204 s to a target (R)AN 204 t. Thetarget (R)AN 204 t may send an N2 Path Switch Request (7208) message toan AMF 218 that includes an indication that the UE 202 has moved to anew target cell, and a list of PDU Sessions to be switched. Depending onthe type of target cell, the target (R)AN 204 t includes appropriateinformation in this message. For the QoS flows to be switched to thetarget (R)AN 204 t, the N2 Path Switch Request message (7208) mayinclude the list of accepted QoS flows.

The AMF 218 may send a N2 SM information via a N11 Message (7210) toeach SMF 220 associated with the list of PDU Sessions and the list ofaccepted QoS flows of each PDU session received in the N2 Path SwitchRequest (7208). For the PDU Sessions to be switched to the Target (R)AN204 t, upon receipt of the N11 Message (7210), each of the SMFs 220 maydetermine whether the existing UPF 212 can continue to serve the UE 202.If the existing UPF 212 cannot continue to serve the UE 202 and it isnot a PDU session anchor, steps 3-11 of clause 4.9.1.2 of TS 23.502(version 0.3.0, published in March 2017), are performed. Otherwise, thefollowing steps (7212) to (7220) may be performed by each of the SMFs220 if their existing UPFs 212 can continue to serve the UE 202. For theactivated PDU session(s) which are not included in the N2 Path SwitchRequest message (7208), the AMF 218 may send separate request(s) to therelevant SMF(s) 220 to notify that the Target (R)AN 204 t does notsupport this PDU Session.

For PDU Sessions requested (accepted) by the Target (R)AN 204 t, the SMF220 may send an N4 Session Modification Request message (7212) to theUPF 212. The message (7212) may include the (R)AN address, and tunnelidentifiers for downlink User Plane. For PDU Sessions rejected by theTarget (R)AN 204 t, the SMF 218 may either release or deactivate the PDUsessions. For the PDU sessions to be released, the SMF 218 may initiatethe PDU Session Release procedure as defined in Clause 4.3.4 of TS23.502. For the PDU sessions to be deactivated, the SMF 218 may send anN4 Session Modification Request (7212) to the UPF 212 for these PDUsessions. The message (7212) indicates the release of (R)AN N3 tunnelinformation such as the (R)AN Address and Tunnel Endpoint Identifier forthe downlink user plane, a Buffering Command, and a Reactivation Timer,and cause code (e.g. Handover rejected, or No Data Activity). It isnoted that the Buffering Command may be used to indicate whether the UPF212 shall buffer the incoming downlink packets. It is also noted thatthe Reactivation Timer may indicate a duration that the UP of adeactivated PDU session remains in deactivated state after the UPF 212removes the (R)AN N3 tunnel information. Before the Reactivation Timerexpires, the UPF 214 may buffer the downlink packets according to theBuffering Command. After the Reactivation Timer expires, the UPF 212 maybuffer the downlink packets according to the Buffering Command. If theUPF 212 receives downlink packets before or after the Reactivation Timerexpires, the UPF 212 may send a downlink packet notification to the SMF220 to initiate a Network Triggered Service Request.

The UPF 212 may returns an N4 Session Modification Response message(7214) to the SMF 220 after the requested PDU Sessions are switched ormodified/deactivated. The message (7214) may include the Tunnelidentifiers for uplink traffic. In order to assist the reorderingfunction in the Target (R)AN 204 t for PDU sessions requiring a pathswitch, the UPF 212 may send one or more “end marker” packets (7216) onthe old path immediately after switching the path. The UPF 212 maystarts sending downlink packets to the Target (R)AN 204 t (7218). TheSMF 220 may send an N11 Message ACK (7220) to the AMF 218 for PDUSessions which have been switched or deactivated successfully. Themessage (7220) may include the CN Tunnel Information, and may indicatewhether the (R)AN N3 tunnel information is updated for PDU session to beswitched UP path switched, or PDU session is deactivated (UPdeactivation, the UP path released). For deactivated PDU sessions, theSMF 220 may store the deactivation state of deactivated PDU session(s).The N11 Message ACK (7220) may include the N2 SM Message for the (R)AN204 to deactivate the PDU Sessions, and a N1 SM Message Container. TheN2 SM Message may include the PDU Session ID(s). The N1 SM MessageContainer may include the Session Deactivation Request that includes thePDU Session ID(s). It is noted that if the AMF 218 sends the SessionDeactivation Request to the UE 202, then the SMF need only inform theAMF 218 about its session deactivation decision, and the SMF 220 doesnot need to send the N1 SM Message Container to the UE 202. It is alsonoted that step (7220) can occur any time after receipt of N4 SessionModification Response message (7214) at the SMF 220.

It is noted that for PDU sessions that Target (R)AN 204 t rejects, theTarget (R)AN 204 t may remove all PDU session contexts before sendingthe path switch request 7208 to the AMF 218. In this case, the N11Message ACK 7220 from the SMF 220 to the AMF 218 may include the N1 SMmessage to be forwarded to the UE 202 only.

Once the N11 Message ACK (7220) is received from all the SMFs 220, theAMF 218 may aggregate the received CN Tunnel Information from theseresponses and send this aggregated information as a part of N2 SMInformation in a N2 Path Switch Request ACK (7222) to the Target (R)AN204 t. The message (7222) may include an indication for each PDU sessionas to whether the N3 connection is switched, and the N2 SM SessionDeactivation Request and the N1 Message Container. If none of therequested PDP Sessions have been switched successfully, the AMF 218 maysend an N2 Path Switch Request Failure message to the Target (R)AN 204t.

It is noted that the AMF may collect N11 Message ACK (7220) from theSMFs 220 that handles the path switched request and may send to theTarget (R)AN 204 t in a separate message. This will reduce the handovertime for the accepted PDU sessions. The AMF 218 may collect N11 MessageACK (7220) from the SMF 220 for deactivated PDU sessions and forward theN2 SM Session Deactivation Requests and N1 SM Session DeactivationRequests in a separate message to the Target (R)AN 204 t. The AMF 218may combine all N2 SM Session Deactivation Requests in one message andsend to Target (R)AN 204 t. The AMF 218 may combine all N1 SM SessionDeactivation Requests in one message and send to the UE 202. Thecombined N2 Session Deactivation Request may include the combined N1 SMSession Deactivation Request.

In the AMF 218, upon receiving the N 11 Message ACK (7222), the AMF 218may store the deactivation state of deactivated PDU sessions, if any. Itis noted that if the AMF 2204 sends the Session Deactivation Request tothe UE 202, then the AMF 218 may send the N1 MM Message Container(including the Session Deactivation Request having the PDU SessionID(s)) to the UE 202. If the Target (R)AN 204 t receives the N2 SMSession Deactivation Request in step (7222), the Target (R)AN 204 t maydelete the PDU Session Context of PDU sessions to be deactivated. The(R)AN 204 then forwards the N1 SM Container (including the SessionDeactivation Request having the PDU Session ID) to the UE 202 by a RRCmessage (7224). It is noted that if the AMF 218 sends the SessionDeactivation Request to the UE 202 in step (7222), then the (R)AN 204may forward the N1 MM Container (including the Session DeactivationRequest having the PDU Session ID) to the UE 202 by a RRC message(7224). The UE 202 may release radio context of deactivated PDUsessions. The UE sends a RRC message (7226) that includes the N1 SMSession Deactivation Response(s) to the SMF 220 for each of N1 SMSession Deactivation Request via Target (R)AN 204 t (7228) and AMF 218(7230). It is noted that if the AMF 218 sends the Session DeactivationRequest to the UE 202 in step (7224), then the UE sends one N1 MMSession Deactivation Response (7228) to the AMF 218 via the Target (R)AN204 t. By sending a Release Resources message (7232) to the Source (R)AN204 s, the Target (R)AN 204 confirms success of the handover. It thentriggers the release of resources with the Source (R)AN 204 s.

It is noted that the Target (R)AN 204 t may send in message (7232) an N2SM Session Deactivation Response message to the SMF 220 to confirm therelease of PDU session contexts for deactivated PDU sessions. The N2 SMSession Deactivation Response may include the N1 SM Session DeactivationResponse (7226) from the UE 202.

It is noted that the Target (R)AN 204 t may send message 7232 to theSource (R)AN 204 s any time after receiving message 7222 from the AMF218, for example before sending message 7224 to the UE 202.

It is noted that the SMF can make decision to either release ordeactivate PDU session. In another embodiment, the SMF always deactivatePDU sessions that Target (R)AN rejects. In the Handover preparation(7202) and Handover Execution (7204), the Target (R)AN may inform the UE202 the PDU sessions that are deactivated. The SMF 220 shall not send N1SM Session Deactivation Request to the UE 202 and N2 SM SessionDeactivation Requests to the Target (R)AN 204 t. Hence, the messages7224 to 7230 are not needed.

It is noted that the in FIG. 72, the PDU deactivation is triggered bythe PDU session rejection due to the Target (R)AN 204 t not havingenough resources. A person skilled in the art may combine the PDUsession deactivation during handover due to inactivity of PDU session inFIG. 63 and PDU session deactivation due to lacks of resources in Target(R)AN in FIG. 72.

FIG. 73 illustrates, in a message flow diagram, an example of a Xn basedinter NG (R)AN handover procedure (7300) with user plan functionrelocation, in accordance with embodiments of the present invention. Theprocedure (7300) may be used to hand over a UE 202 from a source (R)AN204 s to a target (R)AN 204 t using Xn when the AMF 218 is unchanged andthe SMF 220 determines that the source UPF 212 s is to be relocated. Thesource UPF 212 s is the UPF which terminates a N3 interface in the 5GC.The presence of an IP connectivity between the source UPF 212 s andsource (R)AN 204 s, and between the target UPF 212 t and target (R)AN204 t is assumed.

The procedure (7300) includes the handover preparation (7302) and thehandover execution (7304). The handover execution (7304) includes theforwarding of data (7306) from a source (R)AN 204 s to a target (R)AN204 t. The target (R)AN 204 t may send downlink data (7308) to the UE202. The UE 202 may send uplink data (7310). The target (R)AN 204 t maysend an N2 Path Switch Request (7312) message to an AMF 218 thatincludes an indication that the UE 202 has moved to a new target cell,and a list of PDU Sessions to be switched. Depending on the type oftarget cell, the target (R)AN 204 t includes appropriate information inthis message. For the QoS flows to be switched to the target (R)AN 204t, the N2 Path Switch Request message (7312) may include the list ofaccepted QoS flows.

The AMF 218 may send a N2 SM information via a N11 Message (7314) toeach SMF 220 associated with the list of PDU Sessions and the list ofaccepted QoS flows of each PDU session received in the N2 Path SwitchRequest (7312). For the PDU Sessions to be switched to the Target (R)AN204 t, upon receipt of the N11 Message (7314), each of the SMFs 220 maydetermine whether the existing UPF 212 can continue to serve the UE 202.If the existing UPF 212 cannot continue to serve the UE 202 and it isnot a PDU session anchor, steps 3-11 of clause 4.9.1.2 of TS 23.502 areperformed. Otherwise, the following steps (7316) to (7328) may beperformed by each of the SMFs 220 if their existing UPFs 212 cancontinue to serve the UE 202. For the activated PDU session(s) which arenot included in the N2 Path Switch Request message (7312), the AMF 218may send separate request(s) to the relevant SMF(s) 220 to notify thatthe Target (R)AN 204 t does not support this PDU Session.

For PDU sessions to be switched, the SMF 220 may then select a newTarget UPF 212 t based on UPF Selection Criteria according to clause6.3.3 of TS 23.501. Target UPF IP address assignment and allocation ofdownlink and uplink tunnel identifiers may be performed by the SMF 220(7316). A N4 Session Establishment Request (including the Target (R)ANaddress, and uplink and downlink tunnel identifiers) message (7318) maybe sent to the Target UPF 212 t. The Target UPF 212 t may then send anN4 Session Establishment Response message (7320) to the SMF 220. The SMF220 may start a timer, to be used in step (7336). The SMF 220 may thensend a N4 Session Modification message (7322) to the PDU session anchor212 a. The PDU session anchor 212 a may responds with a N4 SessionModification Response message (7324). At this point, the PDU sessionanchor 212 a may start sending downlink packets (7326) to the Target(R)AN 204 t using the address and tunnel identifiers of the Target (R)AN204 t via the Target UPF 212 t.

The SMF 220 may then send a N11 Message ACK (7328) (including CN TunnelInformation) to the AMF 218. Steps (7332) and (7334) may be similar tosteps 7 and 10 defined in clause 4.9.1.1 of TS 23.502. Once the timerhas expired after step (7320), the SMF 220 may initiate a Source UPF 212s release procedure by sending an N4 Session Termination Request message(7336) to the Source UPF 212 s. The message (7336) may include a ReleaseCause (or cause code). The Source UPF 212 s may acknowledge with an N4Session Termination Response message (7338) to the SMF 220 to confirmthe release of resources.

A Service Request procedure may be used by a 5G UE 202 in the CM IDLEstate to request the establishment of a secure connection to an AMF 218.The UE 202 in the CM IDLE state may initiate the Service Requestprocedure in order to send uplink signalling messages, user data, orresponse to a network paging request. After receiving the ServiceRequest message, the AMF 218 may perform authentication, and the AMF 218may perform the security procedure. After the establishment of a securesignalling connection to an AMF 218, the UE 202 or network may sendsignalling messages, e.g., PDU session establishment from UE 202 to thenetwork, or the SMF 220, via the AMF 218, may start the User Planeresource establishment for the PDU sessions requested by the networkand/or indicated in the Service Request message.

For any Service Request, the AMF 218 may respond with a Service Responsemessage to synchronize PDU session status between the UE 202 and thenetwork. The AMF 218 may also respond with a Service Reject message tothe UE 202, if the Service Request cannot be accepted by network. For aService Request due to user data, the network may take further actionsif the User Plane resource establishment is not successful. If thecurrent UPF 212 terminating N3 connection cannot be connected to (R)AN204, the SMF 220 may reselect a new N3-terminating UPF 212. It is notedthat the procedure in clause 4.2.3.2 is not applicable for an accessnetwork (once the UE 202 is registered in the network) in which the UE202 is always considered as in the CM-CONNECTED state, and in which theUser Plane resource is always considered established for an active PDUsession.

FIG. 74 illustrates, in a message flow diagram, an example of a UEtriggered Service Request procedure (7400), in accordance withembodiments of the present invention. The UE 202 initiates a servicerequest procedure to activate a PDU session. The 5G Core Network mayreselect a new UPF terminating N3 connection. The Source UPF 204 s andTarget UPF 204 t are not the UPF 212 that provides the N6 connection toData Network (DN). The UE 202 may send to the (R)AN 204 a MM NAS ServiceRequest message (7402). The message (7402) may include PDU sessionID(s), security parameters, and a PDU session status. The UE 202 maysend a NAS message Service Request (7402) towards the AMF 218encapsulated in an RRC message to the (R)AN 204. If the Service Requestis triggered for user data, the UE 202 may include the PDU session ID(s)in the NAS Service Request message to indicate the PDU session(s) thatthe UE 202 is to use. If the Service Request is triggered for signallingonly, the UE 202 does not include any PDU session ID. When thisprocedure is triggered for a paging response, if the UE 202 needs to usesome PDU session(s), the UE 202 may include the PDU session ID(s) in theMM NAS Service Request message to indicate the PDU session(s) that theUE 202 is to use. Otherwise the UE 202 will not include any PDU sessionID. The PDU session status indicates the PDU sessions available in theUE 202.

Next, the (R)AN 204 may send to the AMF218 a N2 Message (7404) thatincludes the MM NAS Service Request, a 5G Temporary ID, Locationinformation, a RAT type, and a RRC establishment cause). If the AMF 218cannot handle the Service Request, it may reject it. A 5G Temporary IDmay be obtained in a RRC procedure. The (R)AN 204 may select the AMF 218according to the Temporary ID. The Location Information and RAT typerelates to the cell in which the UE 202 is camped. Based on the PDUsession status, the AMF 218 may initiate a PDU session release procedureif the PDU session is not available in the UE 202. Next, if the ServiceRequest was not sent integrity protected, or integrity protection isindicated as failed, the AMF 218 may initiate a NASauthentication/security procedure (7406) as defined in clause 4.6 of TS23.502. If the UE 202 triggered the Service Request to establish asignalling connection only, after the security exchange, the UE 202 andthe network can send signalling and steps (7408) and (7420) to (7430)are skipped.

Next, the AMF 218 may send to the SMF 220 a N11 Message (7408) that mayinclude the PDU session ID(s), the Location Information, and the RATtype. If the MM NAS Service Request message includes PDU session ID(s),or if this procedure is triggered by the SMF 220 but the PDU session IDsfrom the UE 202 correlates to other SMFs 220 than the one triggering theprocedure, the AMF 218 may send a N11 message to SMF(s) 220 associatedwith the PDU session ID(s). If the current Source UPF 212 s cannot servethe requested PDU session, the SMF 220 may select a Target UPF 212 t(7410) based on criteria in Clause 6.3.3 of TS 23.501. Otherwise, if theSource UPF 212 s can serve the requested PDU session, steps (7412) to(7418), (7438) to (7440), and (7444) to (7446) are skipped.

Once the Target UPF 212 t is determined, the SMF 220 may assign N3tunnel information (such as a N3 uplink Tunnel Endpoint Identifier) andN9 tunnel information (such as a N9 Anchor UPF Address and a N9 uplinkTunnel Endpoint Identifier). The SMF 220 may then send a N4 Message PDUSession Establishment Request message (7412) to the Target UPF 212 t.The message (7412) may include the UE and PDU Session Context, includingthe PDU Session ID, the QoS policy, the charging policy, and N3 and N9tunnel information. Next, the Target UPF 212 t may prepare resources tosupport the PDU session. The Target UPF 212 t may send a N4 MessageSession Establishment Response message (7414) to the SMF 220. Themessage (7414) may include a UE identifier (such as SUPI) and the PDUSession ID. Alternatively, the message (7414) may include a transactionID representing both UE identifier and PDU session ID.

Next, the SMF 220 may send a N4 Message Session Modification Requestmessage (7416) to the Anchor UPF 212 a (i.e., Session Anchor UPFproviding N6 connection to the DN). The message (7416) may include theUE identifier such as SUPI, and the N9 Target UPF 212 t tunnelinformation such as the Target UPF Address and the N9 downlink TunnelEndpoint Identifier. Next, the Anchor UPF 212 a may update the TargetUPF tunnel information. The Anchor UPF 212 a may send a N4 MessageSession Modification Response message (7418) to the SMF 220. The SMF 220may sent send a N11 Message (7420) to the AMF 218. The message (7420)may include the N2 SM information such as the PDU Session ID, the QoSprofile, the CN N3 Tunnel Info, and the S-NSSAI.

Upon reception of the N11 Message (7408), each SMF 220 may send a N11Message (7420) to the AMF 218 to establish the User Plane(s) for the PDUsessions. The N2 SM information may include information that the AMF 218can provide to the (R)AN 204. If a Target UPF212 t is selected (7410),the SMF 220 may start a timer to be used in steps (7444) and (7446). TheAMF 218 may send a N2 Request message (7422) to the (R)AN 204. Themessage (7422) may include the N2 SM information received from the SMF220, the security context, the AMF Signalling Connection ID, a HandoverRestriction List, and a MM NAS Service Accept. The (R)AN 204 may storethe Security Context, the AMF Signalling Connection Id, the QoSInformation for the QoS Flows of the PDU Sessions that are activated,and the N3 Tunnel IDs in the UE RAN context. The MM NAS Service Acceptmay include the PDU session status in the AMF 218. The AMF 218 mayinclude at least one N2 SM information from the SMF 220 if the procedureis triggered for a PDU session User Plane setup. The AMF 218 may sendadditional N2 SM information from the SMFs 220 in separate N2 message(s)(e.g., a N2 tunnel setup request), if any. Alternatively, if multipleSMFs 220 are involved, the AMF 218 may send one N2 Request message tothe (R)AN 204 after the N11 messages from SMFs 220 are received. In suchcases, the N2 Request message may include the N2 SM information receivedin each of the N11 messages, and information to enable the AMF 218 toassociate responses to relevant SMFs 220.

The (R)AN 204 may perform a RRC Connection Reconfiguration (7424) withthe UE 202 UE depending on the QoS Information for the QoS Flows of theactivated PDU Sessions and Data Radio Bearers. The User Plane securitymay be established at this step (7424). The (R)AN 204 may forward the MMNAS Service Accept to the UE 202. The UE 202 may locally delete thecontext of the PDU sessions that are not available in the 5G CN. Afterthe User Plane radio resources are setup, the uplink data from the UE202 may now be forwarded to the (R)AN 204 (7426). The 5G (R)AN 204 maysend the uplink data to the UPF 212 address and Tunnel ID provided inthe step (7422). The (R)AN 204 may send a N2 Request ACK message (7428)to the AMF 218. The message (7428) may include the N2 SM informationthat includes the (R)AN Tunnel info, the List of accepted QoS Flows forthe PDU Sessions activated, and the List of rejected QoS Flows for thePDU Sessions activated. The N2 SM information may include the (R)AN 204tunnel information. The (R)AN 204 may respond to the N2 SM informationwith a separate N2 message (e.g., a N2 tunnel setup response) if the AMF218 sends a separate N2 message in step (7422). If multiple N2 SMinformation are included in the N2 Request message in step (7422), theN2 Request ACK (7428) may include the multiple N2 SM information, andinformation to enable the AMF 218 to associate the responses to therelevant SMF 220.

The AMF 218 may then send a N11 Message (7430) per accepted PDU Sessionto the SMF 220. The message (7430) may include the N2 SM information(that includes the (R)AN Tunnel information and the List of accepted QoSFlows), and the RAT Type. If the AMF 218 received N2 SM information (oneor multiple) in step (7420), then the AMF 218 may forward the N2 SMinformation to the relevant SMF 220. If the UE Time Zone has changedcompared to the last reported UE Time Zone, then the AMF 218 may includethe UE Time Zone IE in this message (7430). If dynamic PCC is deployed,the SMF 220 may optionally initiate a PDU-CAN Session Modification(7432) and provide new location information to the PCF 222.

If a Source UPF 212 s is selected in step (7410), and if a User Plane isto be setup or modified, the SMF 220 may initiate a N4 SessionModification Request procedure by sending a N4 Modification Requestmessage (7434) to the Source UPF 212 s. The message (7434) may includethe (R)AN Tunnel Information. The Source UPF 212 s may send a N4 SessionModification Response message (7436) to the SMF 220. If a Target UPF 212t is selected in step (7410), and if a User Plane is to be setup ormodified, the SMF 220 may initiate a N4 Session Modification procedureby sending a N4 Message PDU Session Modification Request to the TargetUPF 212 t (7438). The message may include the (R)AN Tunnel Information.The Target UPF 212 t may send a N4 Session Modification Response message(7440) to the SMF 220.

The SMF may send a N11 Message ACK message (7442) to the AMF 218. Themessage (7442) may include the PDU Session ID. The SMF 220 may indicatea successful session activation message (7442) to the AMF 218. The AMF218 may store the activated state of the PDU session. Once the timer setin step (7420) expires, the SMF 220 may send a N4 Message SessionTermination Request (7444) to the Source UPF 212 s. The message (7440)may include a UE 202 identifier (e.g., a SUPI) and a PDU Session ID. TheSource UPF 212 s may delete the PDU session context. The Source UPF 212may then send a N4 Message Session Termination Response message (7446)to the to the SMF 220.

In FIG. 74, the UPF terminating N3 connection is not the UPF 212providing the N6 connection to Data Network (DN) 208. In case the UPFterminating N3 connection is also the UPF 212 that provides N6connection to DN 208, the 5G Core Network (SMF 220) can insert a UPFfunction to terminate the N3 connection and connect the new UPF functionto the UPF function providing N6 connection.

A Service Request procedure may be used by a 5G UE 202 in theCM-CONNECTED state to request the establishment of User Plane resourcesfor the PDU sessions. It is noted that the network may take furtheractions if the User Plane resource establishment is not successful. Itis also noted that the procedure shown in FIG. 75 is used for an accessnetwork (once the UE 202 is registered in the network) in which the UE202 is always considered as in the CM-CONNECTED state, and in which theUser Plane resource is always considered established for an active PDUsession.

FIG. 75 illustrates, in a message flow diagram, an example of a UEtriggered Service Request procedure in CM-CONNECTED state (7500), inaccordance with embodiments of the present invention. The UE 202 maysend a MM NAS Service Request message (7402) to the (R)AN 204. Themessage (7402) may include the PDU session ID(s). The UE 202 may sendthe NAS message Service Request towards the AMF 218 encapsulated in anRRC message to the (R)AN 204. The MM NAS Service Request message may beencrypted and integrity protected. The PDU session ID(s) in the NASmessage Service Request message may indicate the PDU session that the UE202 selects to activate.

The (R)AN 204 may then send a N2 Message (7404) to the AMF 218. Themessage (7404) may include the MM NAS Service Request. If the ServiceRequest (7404) cannot be handled by the AMF 218, the AMF 218 may rejectit. The (R)AN 204 may forwards the MM NAS Service Request message to theAMF 218 based on the existing N2 connection. The AMF 218 may send a N11Message (7408) to the SMF 220. The message may include the PDU sessionID(s), the Location Information (of the UE, could be in the format of(R)AN Address), and the RAT type. If the current Source UPF 212 s cannotserve the requested PDU session, the SMF 212 s may select a Target UPF212 t (7410) based on criteria in Clause 6.3.3 of TS 23.501. Otherwise,if the Source UPF 212 s can serve the requested PDU session, steps(7412) to (7418) and (7438), (7440), (7444) and (7446) are skipped.

Once the Target UPF 212 t is determined, the SMF 220 may assign N3tunnel information (such as a N3 uplink Tunnel Endpoint Identifier) andN9 tunnel information (such as a N9 Anchor UPF Address and a N9 uplinkTunnel Endpoint Identifier). The SMF 220 may then send a N4 Message PDUSession Establishment Request message (7412) to the Target UPF 212 t.The message (7412) may include the UE and PDU Session Context, includingthe PDU Session ID, the QoS policy, the charging policy, and N3 and N9tunnel information. Next, the Target UPF 212 t may prepare resources tosupport the PDU session. The Target UPF 212 t may send a N4 MessageSession Establishment Response message (7414) to the SMF 220. Themessage (7414) may include a UE identifier (e.g., SUPI) and the PDUSession ID.

Next, the SMF 220 may send a N4 Message Session Modification Requestmessage (7416) to the Anchor UPF 212 a (i.e., Session Anchor UPF). Themessage (7416) may include the SUPI, and the N9 Target UPF 212 t tunnelinformation such as the Target UPF Address and the N9 downlink TunnelEndpoint Identifier. Next, the Anchor UPF 212 a may update the TargetUPF tunnel information. The Anchor UPF 212 a may send a N4 MessageSession Modification Response message (7418) to the SMF 220. The SMF 220may sent send a N11 Message (7420) to the AMF 218. The message (7420)may include the N2 SM information such as the PDU Session ID, the QoSprofile, the CN N3 Tunnel Info, and the S-NSSAI.

Upon reception of the N11 Message (7408), each SMF 220 may send a N11Message (7420) to the AMF 218 to establish the User Plane(s) for the PDUsessions. The N2 SM information may include information that the AMF 218can provide to the (R)AN 204. If a Target UPF212 t is selected (7410),the SMF 220 may start a timer to be used in steps (7444) and (7446). TheAMF 218 may send a N2 Request message (7422) to the (R)AN 204. Themessage (7422) may include the N2 SM information received from the SMF220, including PDU Session ID, QoS profile, CN N3 Tunnel Info, S-NSSAI,and a MM NAS Service Accept. If there are multiple PDU Sessions thatinvolves multiple SMFs 220, the AMF 218 does not need to wait forresponses from all SMFs 220 in step (7420).

The RAN performs a RRC Connection Reconfiguration (7424) with the UE 202depending on the QoS Information for the QoS Flows of the PDU Sessionsand activated Data Radio Bearers. The (R)AN 204 may forward the MM NASService Accept to the UE 202. After the User Plane radio resources forthe selected PDU session are setup, the uplink data from the UE 202 cannow be forwarded (7426) to the (R)AN 204. The 5G (R)AN 204 may send theuplink data to the UPF address and Tunnel ID provided in the step(7422). The (R)AN 204 may next send a N2 Request ACK message (7428) tothe AMF 218. The message (7428) may include the N2 SM information, suchas the (R)AN Tunnel info, the List of accepted QoS Flows for theactivated PDU Sessions, and the List of rejected QoS Flows for theactivated PDU Sessions). The message (7428) may include the N2 SMinformation(s), e.g. the (R)AN tunnel information. The (R)AN may send N2SM information with separate N2 messages (e.g., N2 tunnel setupresponse) in step (7422). The AMF 218 may next send a N11 Message (7430)per accepted PDU Session to the SMF 220. The message (7430) may includethe N2 SM information (including the (R)AN Tunnel information, the Listof accepted QoS Flows, and the List of rejected QoS Flows). If dynamicPCC is deployed, the SMF 220 may optionally initiate a PDU-CAN SessionModification (7432) and provide new location information to the PCF 222.

The SMF 220 may send a N4 Session Modification Request message (7434) tothe Source UPF 212 s. The message (7434) may include the (R)AN tunnelinformation and the List of accepted QoS Flows. If a Source UPF 212 s isselected in step (7412), and if a User Plane is to be setup or modified,the SMF 220 may initiate a N4 Session Modification procedure by sendingthe N4 Session Modification Request message (7434), providing the (R)ANTunnel Information (e.g., (R)AN Address and (R)AN N3 Tunnel EndpointID). The Source UPF 212 s may send a N4 Session Modification Responsemessage (7436) to the SMF 220. If a Target UPF 212 t is selected in step(7410), and if a user plane is to be setup or modified, the SMF 220 mayinitiate a N4 Session Modification procedure by sending a N4 SessionModification Request (7438) to the Target UPF 212 t that provides the(R)AN Tunnel Information (e.g., (R)AN Address and (R)AN N3 TunnelEndpoint ID). The Target UPF 212 t may send a N4 Session ModificationResponse message (7440) to the SMF 220. The SMF 220 may send a N11Message ACK message (7442) to the AMF 218. The message (7442) includesthe PDU Session ID. The SMF 220 may indicate successful sessionactivation to the AMF 218. The AMF 218 may then store the activatedstate of PDU session. If the Target UPF 212 t is selected in step(7410), once the timer set in step (7422) expires, the SMF 220 may senda N4 Message Session Termination Request message (7444) to the SourceUPF 212 s. The message (7444) may include a UE 202 identifier (e.g., aSUPI) and a PDU Session ID. The Source UPF 212 s may delete the PDUsession context and send a N4 Message Session Termination Responsemessage (7646) to the SMF 220.

A Network triggered Service Request procedure may be used when thenetwork needs to signal (e.g., N1 signalling to a UE 202, aMobile-terminated SMS, a PDU session User Plane resource establishmentto deliver mobile terminating user data) with a UE 202. If the UE 202 isin the CM-IDLE state or the CM-CONNECTED state, the network may initiatea network triggered Service Request procedure. If the UE 202 is in theCM-IDLE state, and asynchronous type communication is not activated, thenetwork may send a Paging Request to the (R)AN/UE. The Paging Requestmay trigger the Service Request procedure in the UE 202. If asynchronoustype communication is activated, the network may store the receivedmessage and forward the message to the (R)AN 204 and/or the UE 202(i.e., synchronize the context with the (R)AN 204 and/or the UE 202)when the UE 202 enters the CM-CONNECTED state.

FIG. 76 illustrates in a message flow diagram, an example of a NetworkTriggered Service Request procedure (7600), in accordance withembodiments of the present invention. When the UPF 212 receives downlinkdata of a PDU session (7602) and there is no (R)AN 204 tunnelinformation stored in the UPF 212 for the PDU session, the UPF 212 maybuffer the downlink data. On arrival of the first downlink data packet(7602), the UPF 212 may send a Data Notification message (7604) to theSMF 220. The message (7604) may include the PDU session ID and thePriority). If the UPF 212 receives additional downlink data packets(7602) for a QoS Flow in the same PDU Session with the same or a lowerpriority than used in any previous Data Notification for this PDUsession, the UPF 212 may buffer these downlink data packets withoutsending a new Data Notification. It is noted that if the UPF 212receives additional downlink data packets for a QoS Flow in the same PDUSession with a higher priority than used in any previous DataNotification for this PDU Session, the UPF 212 may send a DataNotification message (7604) to the SMF 220 indicating the higherpriority. If the Paging Policy Differentiation feature (as specified inTS 23.501 clause 5.2.X) is supported by the UPF 212, and if it isactivated by the SMF 220 for this N4 session, the UPF 212 may alsoinclude the DSCP in TOS (IPv4)/TC (IPv6) value from the IP header of thedownlink data packet. If the SMF 220, while waiting for the User Planeto be established in the UPF 212, receives a N11 message notifying thenew AMF 218 serving the UE 202 from the new AMF 218, the SMF 220 mayresend the Data Notification message (7604) to the new AMF 218. The SMF220 may send a Data Notification ACK (7606) to the UPF 212.

Upon reception of a Data Notification message (7604), the SMF 220 maydetermine the AMF 218, and send a N11 message (7608) to the AMF 218including the Priority and PDU Session ID received in the DataNotification message (7604). The message (7608) may include the UEPermanent ID, the PDU session ID, the N2 SM information (including thePDU Session ID, the QoS profile, the CN N3 Tunnel Info, and theS-NSSAI), the Priority, and the Paging Policy Indication. If the SMF220, while waiting for the User Plane Connection to be activated,receives any additional Data Notification message (7604) for the samePDU session but with higher priority than indicated in any previous DataNotification for this PDU session, the SMF 220 may send a new N11message (7608) indicating the higher priority and PDU Session ID to theAMF 218. If the SMF 220, while waiting for the User Plane to beactivated, receives an N11 message response (7606) from an AMF 218 otherthan the one to which the SMF 220 sent an N11 message, the SMF 220 maysend the N11 message to this AMF 218. When supporting Paging PolicyDifferentiation, the SMF 220 may indicate in the N11 message (7608) thePaging Policy Indication related to the downlink data (7602) thattriggered the Data Notification message (7604). It is noted that the AMF218 may receive request message(s) from other network functions whichmay lead to signalling towards the UE/RAN, e.g., network initiateddetach, and SMF 220 initiated PDU session modification. If the UE 202 isin the CM-CONNECTED state, and the AMF 218 only delivers N1 messagetowards the UE 202, the flow continues in step (7618) below. If the UE202 is in the CM-IDLE state, and the AMF 218 determines that the UE 202is not reachable for paging, the AMF 218 may either send an N11 messageto the SMF (7610), or other network functions from which AMF 218received the request message in step (7608) indicating the UE 202 is notreachable, or the AMF 218 performs an asynchronous type communicationand stores the N11 message (7610). If asynchronous type communication isinvoked and the AMF 218 stored an N11 message, the AMF 218 may initiatecommunication with the UE 202 and (R)AN 204 when the UE 202 isreachable, e.g., when the UE 202 enters the CM-CONNECTED state. If theRegistration procedure with an AMF 218 change is in progress when theold AMF 218 receives a N11 message (7608), the old AMF 218 may rejectthe N11 message with an indication that the N11 message has beentemporarily rejected. The SMF 220 may notify the UPF 212 about the UserPlane setup failure (7612). Upon receiving the information that the N11message requested from an SMF 220 has been temporarily rejected, andreceiving the Downlink Data Notification from UPF 212, the SMF 220 mayrequest the UPF 212 to apply extended buffering.

The AMF 218 may send a Paging message (7740) to a (R)AN node. If the UE202 is in CM-CONNECTED state, the AMF 218 performs steps in a UEtriggered Service Request procedure (7618) to activate the User PlaneConnection for this PDU session (i.e., establish the radio resources andN3 tunnel). The rest of this procedure may be omitted. If the UE 202 isin RM-REGISTERED state, in the CM-IDLE state and reachable, the AMF 218may send a Paging message (7740) to (R)AN node(s) belonging to theRegistration Area(s) in which the UE 202 is registered. The Paging mayinclude the NAS ID for paging, the Registration Area list, the PagingDRX length, and the Paging Priority indication. When supporting PagingPolicy Differentiation, the AMF 218 may include a Paging PolicyIndication in the Paging Request message.

Paging strategies may be configured in the AMF 218 for differentcombinations of DNN, Paging Policy Indication, PDU Session IDs from theSMF 220 when available, and other PDU Session context informationidentified by the PDU Session ID received in the N11 message. Pagingstrategies may include: a paging retransmission scheme (e.g., howfrequently the paging is repeated or with what time interval);determining whether to send the Paging message (7740) to the (R)AN nodesduring certain AMF 218 high load conditions; whether to apply sub-areabased paging (e.g., first page in the last known cell-id or TA andretransmission in all registered TAs). The AMF 218 and the (R)AN204 maysupport further paging optimisations in order to reduce the signallingload and the network resources used to successfully page a UE 202 by oneor several of the following means:

-   -   by the AMF 218 implementing specific paging strategies (e.g.,        the N2 Paging message (7740) is sent to the (R)AN nodes that        last served the UE 202);    -   by the AMF 218 considering Information On Recommended Cells And        RAN nodes provided by the (R)AN 204 at transition to the CM-IDLE        state. The AMF 218 takes the (R)AN nodes related part of this        information into account to determine the (R)AN nodes to be        paged, and provides the information on recommended cells within        the N2 Paging message to each of these (R)AN nodes;    -   by the (R)AN 204 considering the Paging Attempt Count        Information provided by the AMF 218 at paging.

If the UE Radio Capability for Paging Information is available in theAMF 218, the AMF 218 may add the UE Radio Capability for PagingInformation in the N2 Paging message (7740) to the (R)AN nodes 204. Ifthe Information On Recommended Cells And (R)AN nodes For Paging isavailable in the AMF 218, the AMF 218 may take that information intoaccount to determine the (R)AN nodes for paging and, when paging a (R)ANnode, the AMF 218 may transparently convey the information onrecommended cells to the (R)AN node. The AMF 218 may include in the N2Paging message(s) the paging attempt count information. The pagingattempt count information may be the same for all (R)AN nodes selectedby the AMF 218 for paging. If (R)AN nodes receive paging messages fromthe AMF 218, the UE 202 may be paged by the (R)AN node (7614).

The AMF 218 may send a N11 message ACK (7616) to the SMF 220. The AMF218 may supervise the paging procedure with a timer. If the AMF 218receives no response from the UE 202 to the Paging Request message(7614), the AMF 218 may apply further paging according to any applicablepaging strategy. If the AMF 218 receives no response from the UE 202,the AMF 218 considers the UE 202 as unreachable and the SM N2 messagecannot be routed to the (R)AN 204. The AMF 218 may then return an “N11message Reject” (7616) with an appropriate “failure cause”, e.g. UEunreachability, to SMF 220 or other network functions to indicate thefailure of “message routing service”, unless the AMF 218 is aware of anongoing MM procedure that prevents the UE 202 from responding, i.e., theAMF 218 receives an N14 Context Request message indicating that the UE202 is performing a Registration procedure with another AMF 218. When an“N11 message Reject” is received, the SMF 220 may informs the UPF 212.

When UE is in the CM-IDLE state, upon reception of the paging request(7614), the UE may initiate the UE triggered Service Request procedure(7618). The AMF 218 may send a N11 message to SMF(s) 220 associated withthe PDU session identified by PDU session ID(s) in a MM NAS ServiceRequest message, if any, but not to the SMF(s) 220 from which itreceives the N11 message in step (7608). The UPF 212 transmits anybuffered downlink data towards the UE 202 via the (R)AN node whichperformed the Service Request procedure (7618). The network may senddownlink signalling (7620) if the procedure is triggered due to arequest from other network entities described in step (7608).

A UE triggered Service Request in CM-IDLE state procedure may be used bya 5G UE 202 in the CM-IDLE state to request the establishment of asecure connection to an AMF 218. The UE 202 in the CM-IDLE state mayinitiate the Service Request procedure in order to send uplinksignalling messages, user data, or response to a network paging request.After receiving the Service Request message, the AMF 218 may performauthentication, and the security procedure. After the establishment of asecure signalling connection to an AMF 218, the UE 202 or network maysend signalling messages, e.g., a PDU session establishment from the UE202 to the network, or the SMF 220, via the AMF 218, may start the UserPlane resource establishment for the PDU sessions requested by thenetwork and/or indicated in the Service Request message. For any ServiceRequest, the AMF 218 may respond with a Service Response message tosynchronize the PDU session status between the UE 202 and the network.The AMF 218 may also respond with a Service Reject message to the UE202, if the Service Request cannot be accepted by network. For ServiceRequest due to user data, they network may take further actions if theUser Plane resource establishment is not successful. It is noted thatthe procedure shown in FIG. 64 is not applicable for an access network(once the UE 202 is registered in the network) in which the UE 202 isalways considered as in the CM-CONNECTED state, and in which the UserPlane resource is always considered established for an active PDUsession.

FIG. 77 illustrates, in a message flow diagram, an example of a UEtriggered Service Request procedure (7700) in CM-CONNECTED state, inaccordance with embodiments of the present invention. The UE 202 maysend a MM NAS Service Request message (6402) to a (R)AN 204. The message(6402) may include the PDU session ID(s). The UE 202 may send the NASmessage Service Request towards the AMF 218 encapsulated in an RRCmessage to the (R)AN. The MM NAS Service Request message may beencrypted and integrity protected. The PDU session ID(s) in the NASmessage Service Request message indicates the PDU session that the UE202 selects to activate.

The (R)AN 204 may send a N2 Message (6404) to the AMF 218. The message(6404) may include the MM NAS Service Request. If the Service Request(6404) cannot be handled by the AMF 218, the AMF 218 may reject it. The(R)AN 204 may forward the MM NAS Service Request message to the AMF 218based on the existing N2 connection. The AMF 218 may then send a N11Message (6408) to SMF(s) 220 associated with the PDU session ID(s). Uponreception of the N11 Message (6408), each SMF 220 may send a N11 Message(6410) to the AMF 218 to establish the User Plane(s) for the PDUsessions. The message (6410) may include the N2 SM information thatincludes the PDU Session ID, the QoS profile, the CN N3 TunnelInformation and the S-NSSAI. The N2 SM information may includeinformation that the AMF 218 may provide to the (R)AN 204.

The AMF 218 may next send a N2 Request message (6412) to (R)AN 204. Themessage (6412) may include the N2 SM information (including the QoSprofile, and the CN N3 Tunnel Information) received from SMF, MM NASService Accept). If there are multiple PDU Sessions that involvesmultiple SMFs 220, the AMF 218 does not need wait for responses from allSMFs 220 in step (6410). The (R)AN 204 may then perform a RRC ConnectionReconfiguration (6414) with the UE 202 depending on the QoS Informationfor the QoS Flows of the activated PDU Sessions and Data Radio Bearers.The (R)AN 204 may forward the MM NAS Service Accept to the UE 202. Ifthe (R)AN 204 accepts at least one of QoS flows, the UE 202 may storethe activated state of the PDU session. Otherwise, the UE 202 mayconsider the Service Request as not accepted by the (R)AN 204; The PDUsession state in the UE remains deactivated.

After the User Plane radio resources for the selected PDU session aresetup, the uplink data from the UE 202 may now be forwarded (6416) tothe (R)AN 204. The 5G (R)AN 204 may send the uplink data to the UPF 212address and Tunnel ID provided in the step (6410). If the (R)AN 204accepts at least one QoS flow, the (R)AN 204 may send a N2 Request ACKmessage (6418) to the AMF 218. The message (6418) may include the PDUSession ID, the N2 SM information (including the (R)AN Tunnelinformation, the List of accepted QoS Flows for the PDU Sessionsactivated, and the List of rejected QoS Flows for the PDU Sessionsactivated). The (R)AN 204 may respond N2 SM information with separate N2messages (e.g., a N2 tunnel setup response). If the (R)AN 204 does notaccept the PDU session, the (R)AN 204 may send a N2 Request ACK message(6418) to the AMF 218 that indicates that the N2 Request is not acceptedand a cause code. The message (6418) may include the N2 SM information(including the PDU Session ID, the PDU Session Reject, and the causecode). The AMF 218 may send a N11 Message (6420) per accepted PDUSession to the SMF 220. The message (6420) may include the PDU SessionID, and the N2 SM information received from (R)AN 204 in step (6418).

If the PDU session is accepted, and if dynamic PCC is deployed, the SMF220 may initiate an IP-CAN Session Modification procedure (6422) andprovide new location information to the PCF 222. If the PDU session isaccepted, and if a User Plane is to be setup or modified the SMFinitiates a N4 Session Modification procedure by sending a N4 SessionUpdate Request (6424) message that provides RAN Tunnel Information and aList of accepted QoS Flows. The UPF 212 may then send to SMF 220 a N4Session Update Response message (6426). The SMF may then send a N11Message ACK message (6428) to the AMF 218. The message may include thePDU Session ID, and the PDU session state. The SMF 220 may indicate thePDU session state (Activated or Deactivated) to the AMF 218.

An Xn based inter NG RAN handover procedure without User Plane functionrelocation may be used to hand over a UE 202 from a source (R)AN 204 sto a target (R)AN 204 t using Xn when the AMF 218 is unchanged and theSMF 220 determines to keep the existing UPF 212. The UPF 212 referred tois the UPF 212 which terminates N3 interface in the 5GC. The presence ofIP connectivity between the Source UPF 212 s and Target UPF 212 t isassumed. If the Target (R)AN 204 does not have enough resources to servesome PDU sessions, the Target (R)AN 204 may notify the SMF 220. The SMF220 may then determine to release or to keep the PDU session. For thePDU session to be released, the SMF 220 may initiate the PDU SessionRelease Procedure. For the PDU session to be kept, the SMF 220 mayperform one of following: 1. Deactivate the N3 tunnel between the Target(R)AN 204 t and the UPF 212; 2. Set the Session-AMBR (Aggregated MaximumBit Rate) to zero; or 3. Deactivate the user plane, including airinterface DRB and N3 tunnel.

FIG. 78 illustrates, in a message flow diagram, an example of an IntraAMF, inter NG-RAN node handover procedure (7800) without Xn interface,in accordance with embodiments of the present invention. Downlink UPdata may be transmitting (7802) between the UPF 212 and the UE 202 viathe S-RAN 204 s. An event may occur that causes the S-RAN 204 s totrigger a relocation via N2 (7804). The S-RAN 204 s may send a HandoverRequired message (7806) to the AMF 218. The message (7806) may include aTarget ID, a Source to Target transparent container, and the PDU sessionIDs. The Source to Target transparent container may include (R)ANinformation created by the S-RAN 204 s to be used by the T-RAN 204 t,and is transparent to 5GCN. All PDU sessions handled by the S-RAN 204 s(i.e., all existing PDU sessions with active UP connections) may beincluded in the Handover Required message (7806), indicating which ofthose PDU session(s) are requested by S-RAN 204 s to handover.

The AMF 218 may send a PDU Handover Request message (7808) to the SMF220. The message may include the PDU session ID and the Target ID, andmay be sent for each PDU-session indicated, by the S-RAN 204 s, as an N2Handover candidate. The PDU session ID indicates a PDU session candidatefor N2 Handover.

The SMF 220 may send a PDU Handover Response message (7810) to the AMF218. The message (7810) may include the PDU session ID and SM N2information. The SMF 220 may select a UPF 212 that supports N3connectivity towards the Target (R)AN node 204 t. The SMF 220 may checkif the N2 Handover for the indicated PDU session can be accepted and mayinclude the result in SM N2 information sent, transparently for the AMF220, to the T-RAN 204 t. If the N2 handover for the PDU session isaccepted, the SM N2 information may also include the PDU session ID, theN3 UP address and Tunnel ID of the UPF 212, and the QoS parameters.

The AMF 218 supervises the PDU Handover Response messages (7812) fromthe involved SMFs 220. The lowest value of the maximum delay indicationsfor the PDU sessions that are candidates for handover gives the maximumtime the AMF 218 may wait for the PDU Handover Response messages (7810)before continuing with the N2 Handover procedure. At the expiry of themaximum wait time, or when all PDU Handover Response messages arereceived, the AMF 218 continues with the N2 Handover procedure (HandoverRequest message in step (7820).

The AMF 218 may send a PDU Handover Cancel message (7814) to the SMF220. The message (7814) may include a PDU session ID. A PDU HandoverResponse message (7810) arriving too late is indicated to the SMF 220allowing the SMF 220 to deallocate a possibly allocated N3 UP addressand Tunnel ID of the selected UPF 212. It is noted that the Modify PDURequest message (7816) sent by the AMF 218 to the SMF 220 and the ModifyPDU Response message (7818) sent by the SFM 220 to the AMF 218 start atstep (7812) and be performed in parallel with that and later steps.

The AMF 218 may send a Handover Request message (7820) to the T-RAN 204t. The message (7820) may include the Source to Target transparentcontainer, the MM N2 information, and the SM N2 info list). The AMF 218may determine and/or select the T-RAN 204 t based on the Target ID. TheAMF 218 may allocate a GUTI valid for the UE 202 in the AMF 218 andtarget TAI. The Source to Target transparent container may be forwardedas received from the S-RAN 204 s. The MM N2 information may include, forexample, security information and the Handover Restriction List. The SMN2 information list may include SM N2 information from the SMFs 220 inthe PDU Handover Response messages received until end of step (7814).

The T-RAN 204 t may send a Handover Request Acknowledge message (7822)to the AMF 218. The message (7822) may include the Target to Sourcetransparent container, the SM N2 response list, and the PDU sessionsfailed to be setup list. The Target to Source transparent container mayinclude a UE 202 container with an access stratum part and a NAS part.The UE 202 container may be sent transparently via the AMF 218 and theS-RAN 204 s to the UE 202. The information provided to the S-RAN 204 smay also include a list of PDU session IDs indicating the PDU sessionsthat failed to be setup and the reason for the failure (e.g., SMF 220decision, SMF 220 response too late, or T-RAN 204 t decision). The SM N2response list includes, per each received SM N2 information and by theSMF 220 accepted PDU session for N2 Handover, a PDU session ID and a SMN2 response indicating the PDU session ID and if T-RAN 204 t acceptedthe N2 Handover request for the PDU session. For each by T-RAN 204 taccepted PDU session for N2 Handover, the SM N2 response may include theN3 UP address and the Tunnel ID of the T-RAN 204 t, and the list ofaccepted QoS flows. For PDU sessions that the T-RAN 204 t rejects, theT-RAN 204 t may set the Session-AMBR is set to zero. Alternatively, theT-RAN 204 t may removed the N3 tunnel information of the UPF 212.

The AMF may send a Modify PDU Request message (7824) to the SMF 220. Themessage (7824) may include the PDU session ID, and the SM N2 response.For each T-RAN 204 t received SM N2 response (included in the SM N2response list), the AMF 218 may send the received SM N2 response to theSMF 220 indicated by the respective PDU Session ID.

The SMF 220 may send a Modify PDU Response message (7826) to the AMF218. The message (7826) may include the PDU session ID, and the message(7826) may be sent for each received Modify PDU Request message (7824).The SMF 220 may perform preparations for N2 Handover by indicating theN3 UP address and the Tunnel ID of T-RAN 204 t to the UPF 212 if the N2Handover is accepted by the T-RAN 204 t. If the N2 Handover is notaccepted by T-RAN 204 t, the SMF 212 may set the Session-AMBR of therejected PDU sessions to zero. The SMF 220 may acknowledge the ModifyRequest message by sending the Modify PDU Response message to the AMF218.

The AMF may send a Handover Command message (7828) to the S-RAN 204 s.The message (7828) may include the Target to Source transparentcontainer, the list of PDU sessions failed to be setup. The Target toSource transparent container may be forwarded as received from the AMF218. The S-RAN 204 s may use the list of PDU sessions that failed to besetup and the indicated reason for failure to determine whether or notto proceed with the N2 Handover procedure.

The S-RAN 204 s may send a Handover Command message (7830) to the UE202. The message may include the UE 202 container. The UE 202 containermay be sent transparently from the T-RAN 204 t via the AMF 218 to theS-RAN 204 s and is provided to the UE 202 by the S-RAN 204 s.

After the UE 202 has successfully synchronized (7832) to the targetcell, it may send the Handover Confirm message (7834) to the T-RAN 204t. The Handover is, by this message, considered by the UE 202 to besuccessful. For rejected PDU sessions, the UE 202 does not send anuplink request for a Reactivation Timer. This timer can be set by aparameter in the UE 202 policy or by a message from the SMF 220.

The T-RAN 204 t may next send to the AMF 218 a Handover Notify message(7838). The handover is, by this message, considered as successful inthe T-RAN 204 t. The AMF 218 may then send a Handover Complete message(7840) to the SMF 220. The message may include the PDU session ID. AHandover Complete message (7840) may be sent per each PDU Session to thecorresponding SMF 220 to indicate the success of the N2 Handover.

The SMF 220 may send a Handover Complete ACK message (7842) to the AMF218. The message (7842) may include the PDU session ID. The SMF 220 mayindicate to the selected UPF 212 that the downlink User Plane for theindicated PDU session may be switched to the T-RAN 204 t. For PDUsessions that are not supported by the T-RAN 204 t, the SMF 220 maynotify the selected UPF 212 to set the Session-AMBR to zero,Reactivation Timer, and Buffering Command. Before the Reactivation Timerexpires, if the UPF does not send a downlink packet notification to theSMF 220 if the UPF 212 receives a downlink packet; these packet may bebuffered or dropped, based on the Buffering Command. If the BufferingCommand is set to TRUE, the downlink packets are buffered. If theBuffering Command is set to FALSE, the downlink packets are dropped. TheSMF 220 may thus confirm reception of the Handover Complete message. TheAMF 218 may send to the S-RAN 204 s a UE Context Release Command ( )message (7846). Next, the S-RAN 204 s may send to the AMF 218 a UEContext Release Complete ( ) message (7848). The source (R)AN 204 s mayrelease its resources related to the UE 202 and respond with the UEContext Release Complete ( ) message (7846).

Unless defined otherwise, all technical and scientific terms used hereinhave the same meaning as commonly understood by one of ordinary skill inthe art to which this invention belongs.

Through the descriptions of the preceding embodiments, the presentinvention may be implemented by using hardware only or by using softwareand a necessary universal hardware platform. Based on suchunderstandings, the technical solution of the present invention may beembodied in the form of a software product. The software product may bestored in a non-volatile or non-transitory storage medium, which can bea compact disk read-only memory (CD-ROM), USB flash disk, or a removablehard disk. The software product includes a number of instructions thatenable a computer device (personal computer, server, or network device)to execute the methods provided in the embodiments of the presentinvention. For example, such an execution may correspond to a simulationof the logical operations as described herein. The software product mayadditionally or alternatively include number of instructions that enablea computer device to execute operations for configuring or programming adigital logic apparatus in accordance with embodiments of the presentinvention.

The AMF 218 is in charge of handling access and mobility management ofthe UE 202, while the SMF 220 is in charge of management of PDUsessions. The AMF may not need to store the state of PDU sessions(activated and deactivated). In some procedures presented earlier inFIG. 59 and FIG. 60 for N2 Release procedure (or UE Context Release in(R)AN procedure) and handover procedures in FIG. 72 and FIG. 74, the AMFmay store the PDU session state. In the following embodiments, the AMFmay not store the PDU session state, which helps to separate thefunctionalities of the AMF and SMF.

An alternative solution to the N2 Release procedure in FIG. 59, which isalso referred to as “UE Context Release in the AN” procedure, isillustrated in FIG. 79, where the AMF may not store the PDU sessionstate. The UE Context Release in the AN procedure may be used to releasea N2 connection and at the same time deactivate PDU sessions when the UE202 enters the CM-IDLE state. FIG. 79 illustrates, in a message flowdiagram, an example of a N2 Release and PDU Session deactivationprocedure (5900), in accordance with embodiments of the presentinvention. The procedure (7900) may begin with the (R)AN 204 and the UE202 performing a Release of Signaling Path over the (R)AN (7902). TheRRC Release procedure (7902) may be similar to the RRC Release procedure(600A) describe above. The (R)AN 204 interacts with the UE 202 torelease the RRC signalling connection. The UE 202 enters the CM-IDLEstate and deactivates all PDU sessions. The (R)AN 204 may send (N2message) a N2 UE Context Release (7904) to the AMF 218. The message(5904) may include a cause code, such as an O&M intervention, UEinactivity, etc. Those skilled in the art will appreciate that, incertain scenarios, step (7902) can be initiated before or in parallelwith step (7904). The AMF 218 may send (N11 message) a UE Mobility EventNotification message (7906) to the SMF(s) 220 which have subscribed tothe UE Mobility Event Notification service of the AMF for the event “UEenters CM-IDLE state”. Other names of event “UE enters CM-IDLE state”could be “N2 Release” or “UE CM state transition to CM-IDLE, etc. Themessage (7906) may include a UE identifier (such as a SUPI), the (R)ANinformation in case the UE has multiple connections to multiple (R)AN,cause code, UE mobility event, list of PDU Session IDs. It should benoted that the SMF 220 may subscribe to a UE mobility Event Notificationservice of the AMF 218 when the PDU session is established or activatedor by a separate subscribe procedure. For example, in TS 23.502, Version0.3.0, published in March 2014, the SMF 220 may subscribe to the UEMobility Event Notification service of the AMF 218, in step 4b of FIG.4.2.3.2-1 of clause 4.2.3.2 “UE triggered Service Request in CM-IDLEstate”, or in step 3b of FIG. 4.2.3.3-1 of clause 4.2.3.3 “UE triggeredService Request in CM-CONNECTED state”, or in step 16 of FIG.4.3.2.2.1-1 of clause 4.3.2.2.1 “Non-roaming and Roaming with LocalBreakout”.

The SMF 220 then sends (N4 message) a N3 Release Request (7908) to theUPF(s) 212. Other names of Release Request message (7908) can be SessionModification Request, or PDU Session Deactivation Request. The message(7908) may include an identifier to identify the UE such as SUPI, or anidentifier to identify PDU Session ID to be deactivated, BufferingCommand, and a Reactivation Timer. The Buffering Command indicateswhether the UPF will buffer the downlink PDU packet received for the UEthen initiates a downlink data notification to the SMF to trigger“Network Triggered Service Request” procedure described in clause4.2.3.3 of TS 23502, Version 0.3.0, published in March 2017. TheReactivation Timer indicates the minimal time the PDU session isdeactivated before the UPF may send a downlink data notification to theSMF if a downlink PDU packet arrives. The UPF 212 then releases the N3(R)AN tunnel information (e.g., the (R)AN IP address and tunnelidentifier) in the UE's PDU Session Context of PDU sessions to bedeactivated. The UPF sends (N4 message) a N3 Release Response (7910) tothe SMF 220 confirming the release of the N3 (R)AN tunnel information.Other names of message (7910) could be Session Modification Response orSession Deactivation Response. The UPF 212 may begin to buffer downlinkpackets of the deactivated PDU sessions. The SMF 220 may not need tosend message (7912) to confirm the reception of message (7906). Insteadof message (7912), the transport layer protocol may use anacknowledgment message upon receiving message (7906). The SMF 220 maythen change the state of the PDU session to Session-IDLE.

The AMF 218 then sends (N2 message) a N2 Release Response (7914) to the(R)AN 204 with a cause code over the N2 interface. Other names ofmessage (7914) could be N2 UE Context Release Request. The AMF 218 maynot need to store the session state of all PDU sessions of the UE 202 toSession-IDLE (or Session Deactivated state). Note that the message(7914) can be sent before, in parallel or after message (7906). If step(7902) was not performed, the RAN 204 and the UE 202 perform a RRCRelease procedure (7916). The RRC Release procedure (7916) may besimilar to the RRC Release procedure (600A) describe above. Other namesof message (7916) could be “Release of Signalling path over the (R)AN”,or “RRC Reconfiguration”. The (R)AN 204 sends a message to UE 202 torelease the RRC connection. The UE 202 enters the CM-IDLE state and allPDU sessions in the UE 202 transition to the Session-IDLE state (or inother words, session deactivated state). Upon receiving RRC connectionrelease confirmation from the UE 202, the (R)AN 204 removes the UEContext. Next, the (R)AN 204 sends (N2 message) a N2 ReleaseConfirmation (7918) to the AMF 218. Another name of message (7918) couldbe “N2 UE Context Release Complete”. Upon receiving the N2 ReleaseResponse (7918) message, the AMF 218 sets the UE CM state to the CM-IDLEstate and releases the N2 connection. It should be noted that the AMF218 may keep or remove the subscription to UE Mobility EventNotification service of the AMF 218 for the SMF(s) service PDU sessions,for some UE mobility events such as “Serving Cell Change”.

It should be noted that the SMF 220 may subscribe to a UE Mobility EventNotification service of the AMF 218 for the event “Serving Cell Change”,when the PDU session is established or activated or by a separatesubscribe procedure. For example, in TS 23.502, Version 0.3.0, publishedin March 2014, the SMF 220 may subscribe to the UE Mobility EventNotification service of the AMF 218, in step 4b of FIG. 4.2.3.2-1 ofclause 4.2.3.2 “UE triggered Service Request in CM-IDLE state”, or instep 3b of FIG. 4.2.3.3-1 of clause 4.2.3.3 “UE triggered ServiceRequest in CM-CONNECTED state”, or in step 16 of FIG. 4.3.2.2.1-1 ofclause 4.3.2.2.1 “Non-roaming and Roaming with Local Breakout”.Consequently, during the handover procedures, for example in FIG. 72,FIG. 73, and FIG. 78, the AMF 218 may send path switch requests to theSMFs 220 which have subscribed to the UE Mobility Event Notificationservice of the AMF 218 for the event “Serving Cell Change”. The SMF 220may subscribe to the UE Mobility Event Notification service of the AMF218 if the SMF serves activated or deactivated PDU sessions. Fordeactivated PDU sessions during handover procedures, the SMF mayrelocate the UPF 212 or release the deactivated PDU session if there isno suitable UPF to serve the PDU session.

By employing the method that AMF may not store PDU session state and theSMF subscribe to the UE Mobility Even Notification, another embodimentof Xn based inter NG (R)AN handover illustrated in FIG. 72 can bederived.

In Handover Preparation (7202) and Handover Execution (7204), if theTarget (R)AN 204 t rejects some PDU sessions, the Target (R)AN 204 tshall not set up any Data Radio Bearer (DRB) for the rejected PDUsessions with the UE 202. The UE shall not release the PDU sessions thathave DRB assigned. The UE shall wait for decision from the SMF whetherto release or deactivate the rejected PDU sessions. These requirementsmay be also applied to the Xn based inter NG (R)AN handover with UPFrelocation described in FIG. 73.

In message (7208) the Target (R)AN 204 t sends N2 Path Switch Request tothe AMF 218. The message (7208) includes a list of accepted PDU sessionand a list of rejected PDU sessions.

The AMF 218 may send a N2 SM information via a N11 Message (7210) toeach SMF 220 associated with the list of PDU Sessions and the list ofaccepted QoS flows of each PDU session received in the N2 Path SwitchRequest (7208). For the PDU Sessions to be switched to the Target (R)AN204 t, upon receipt of the N11 Message (7210), each of the SMFs 220 maydetermine whether the existing UPF 212 can continue to serve the UE 202.If the existing UPF 212 cannot continue to serve the UE 202 and it isnot a PDU session anchor, steps 3-11 of clause 4.9.1.2 of TS 23.502(version 0.3.0, published in March 2017), are performed. Otherwise, thefollowing steps (7212) to (7220) may be performed by each of the SMFs220 if their existing UPFs 212 can continue to serve the UE 202.

For the rejected PDU session(s), the AMF 218 may send separaterequest(s) to the relevant SMF(s) 220 to notify that the Target (R)AN204 t does not support this PDU Session. The AMF 218 may send separaterequest(s) to the SMF(s) 220, which have subscribed to the UE MobilityEven Notification triggered by Serving Cell Change. The message includesAddress of the Target (R)AN.

For PDU Sessions requested (accepted) by the Target (R)AN 204 t, the SMF220 may send an N4 Session Modification Request message (7212) to theUPF 212. The message (7212) may include the (R)AN address, and tunnelidentifiers for downlink User Plane. For PDU Sessions rejected by theTarget (R)AN 204 t, the SMF 218 may either release or deactivate the PDUsessions. For the PDU sessions to be released, the SMF 218 may initiatethe PDU Session Release procedure as defined in Clause 4.3.4 of TS23.502. For the PDU sessions to be deactivated, the SMF 218 may send anN4 Session Modification Request (7212) to the UPF 212 for these PDUsessions. The message (7212) may indicate the release of (R)AN N3 tunnelinformation such as the (R)AN Address and Tunnel Endpoint Identifier forthe downlink user plane, a Buffering Command, and a Reactivation Timer,and cause code (e.g. Handover rejected, or No Data Activity). It isnoted that the Buffering Command may be used to indicate whether the UPF212 shall buffer the incoming downlink packets. It is also noted thatthe Reactivation Timer may indicate a duration that the UP of adeactivated PDU session remains in deactivated state after the UPF 212removes the (R)AN N3 tunnel information. Before the Reactivation Timerexpires, the UPF 214 may buffer the downlink packets according to theBuffering Command. After the Reactivation Timer expires, the UPF 212 maybuffer the downlink packets according to the Buffering Command. If theUPF 212 receives downlink packets before or after the Reactivation Timerexpires, the UPF 212 may send a downlink packet notification to the SMF220 to initiate a Network Triggered Service Request.

For deactivated PDU sessions, the SMF may decide to select a new UPFfunction. In case a new UPF is selected, the SMF sends PDU sessioncontext to the new UPF and requests the old UPF to release the PDUsession context. Alternatively, the SMF may set up a new N3-terminatingUPF and connect the new N3-terminating UPF with the old UPF.

The UPF 212 may returns an N4 Session Modification Response message(7214) to the SMF 220 after the requested PDU Sessions are switched ormodified/deactivated. The message (7214) may include the Tunnelidentifiers for uplink traffic. In order to assist the reorderingfunction in the Target (R)AN 204 t for PDU sessions requiring a pathswitch, the UPF 212 may send one or more “end marker” packets (7216) onthe old path immediately after switching the path. The UPF 212 maystarts sending downlink packets to the Target (R)AN 204 t (7218). TheSMF 220 may send an N11 Message ACK (7220) to the AMF 218 for PDUSessions which have been switched or deactivated successfully. Forswitched PDU sessions, the message (7220) may include the N2 SM message,which includes N3 CN Tunnel Information. For deactivated PDU sessions,the message 7220 may contain N1 SM Message Container containing SessionDeactivation Request and PDU Session IDs. The SMF may store thedeactivation state of deactivated PDU session(s).

Once the N11 Message ACK (7220) is received from all the SMFs 220, theAMF 218 may aggregate the received N2 SM messages and N1 SM messages ina N2 Path Switch Request ACK (7222) to the Target (R)AN 204 t. If noneof the requested PDP Sessions have been switched successfully, the AMF218 may send an N2 Path Switch Request Failure message to the Target(R)AN 204 t.

It is noted that the AMF may collect N11 Message ACK (7220) from theSMFs 220 that handles the path switched request for accepted PDUsessions and may send to the Target (R)AN 204 t in a separate message.This will reduce the handover time for the accepted PDU sessions. TheAMF 218 may collect N11 Message ACK (7220) from the SMF 220 for rejectedPDU sessions and transfers the N1 SM Message Containers in a separatemessage to the Target (R)AN 204 t.

If the Target (R)AN 204 t receives the N1 SM Message Container in step(7222), the Target (R)AN 204 t forwards the N1 SM Message Container(including the Session Deactivation Request having the PDU Session ID)to the UE 202 by a RRC message (7224). The UE stores the deactivatedstate of PDU session(s). The UE 202 may release radio context ofdeactivated PDU sessions. The UE sends a RRC message (7226) thatincludes the N1 SM Session Deactivation Response(s) and PDU SessionID(s) of deactivated PDU sessions to the SMF 220 via Target (R)AN 204 tand AMF 218. By sending a Release Resources message (7232) to the Source(R)AN 204 s, the Target (R)AN 204 confirms success of the handover. Itthen triggers the release of resources with the Source (R)AN 204 s.

In the above description, the Target (R)AN 204 t sends the N1 SessionDeactivation Request message received from the SMF 220 to the UE 202 inthe message (7224). Alternatively, the Target (R)AN 204 t may forwardthe N1 Session Deactivation Request to the Source (R)AN 204 s. TheSource (R)AN 204 s then may forward the N1 Session Deactivation Requestto the UE via another RRC message similar to the message (7224). The UEacknowledges the PDU session deactivation by sending an N1 SessionDeactivation Response to the SMF. This message is delivered to eitherthe Source (R)AN 204 s or Target (R)AN 204 t by the same RRC message(7226). The Source (R)AN 204 s or Target (R)AN 204 t forwards the N1Session Deactivation Response to the AMF 218 by the same message (7228);the AMF 218 then forwards the N1 Session Deactivation Response to theSMF 220 by the same message (7230).

By employing the method that AMF may not store PDU session state and theSMF subscribe to the UE Mobility Even Notification, another embodimentof Intra AMF, inter NG-RAN node handover without Xn interface can bederived as follows. FIG. 78 illustrates, in a message flow diagram, anexample of an Intra AMF, inter NG-RAN node handover procedure (7800)without Xn interface, in accordance with embodiments of the presentinvention. Downlink UP data may be transmitting (7802) between the UPF212 and the UE 202 via the S-RAN 204 s. An event may occur that causesthe S-RAN 204 s to trigger a relocation via N2 (7804). The S-RAN 204 smay send a Handover Request message (7806) to the AMF 218. The message(7806) may include a Target ID, a Source to Target transparentcontainer, and the PDU session IDs. The Source to Target transparentcontainer may include (R)AN information created by the S-RAN 204 s to beused by the T-RAN 204 t, and is transparent to 5GCN. All PDU sessionshandled by the S-RAN 204 s (i.e., all existing PDU sessions with activeUP connections) may be included in the Handover Required message (7806),indicating which of those PDU session(s) are requested by S-RAN 204 s tohandover.

The AMF 218 may send a PDU Handover Request message (7808) to the SMF220. The message may include the PDU session ID and the Target ID, andmay be sent for each PDU-session indicated, by the S-RAN 204 s, as an N2Handover candidate. The PDU session ID indicates a PDU session candidatefor N2 Handover. The AMF 218 may send separate message to the SMF 220that has subscribed to the UE Mobility Event Notification. The messageincludes Target (R)AN. The SMF 220 may decide to select a new UPF toserve the deactivated PDU sessions. If a new UPF is selected, the SMF220 sends session establishment request with PDU session contexts to thenewly selected UPF. After that, the SMF requests the old UPF to releasethe PDU session contexts. Alternatively, the SMF may set up the N9connection between the new UPF and the old UPF. The AMF 218 may sendseparate UE Mobility Event Notification message (7808) to the SMF 220,which SMF subscribes to the “UE Mobility Event Notification” service ofAMF in clause 5.2.2.2 of TS 23.502, Version 0.3.0, published in March2017, for the event of Serving Cell Change. The notification may includePDU session ID(s) new serving cell, which is Target ID.

The SMF 220 may send a PDU Handover Response message (7810) to the AMF218. The message (7810) may include the PDU session ID and SM N2information. The SMF 220 may select a UPF 212 that supports N3connectivity towards the Target (R)AN node 204 t. The SMF 220 may checkif the N2 Handover for the indicated PDU session can be accepted and mayinclude the result in SM N2 information sent, transparently for the AMF220, to the T-RAN 204 t. If the N2 handover for the PDU session isaccepted, the SM N2 information may also include the PDU session ID, theN3 UP address and Tunnel ID of the UPF 212, and the QoS parameters.

The AMF 218 supervises the PDU Handover Response messages (7812) fromthe involved SMFs 220. The lowest value of the maximum delay indicationsfor the PDU sessions that are candidates for handover gives the maximumtime the AMF 218 may wait for the PDU Handover Response messages (7810)before continuing with the N2 Handover procedure. At the expiry of themaximum wait time, or when all PDU Handover Response messages arereceived, the AMF 218 continues with the N2 Handover procedure (HandoverRequest message in step (7820).

The AMF 218 may send a PDU Handover Cancel message (7814) to the SMF220. The message (7814) may include a PDU session ID. A PDU HandoverResponse message (7810) arriving too late is indicated to the SMF 220allowing the SMF 220 to deallocate a possibly allocated N3 UP addressand Tunnel ID of the selected UPF 212. It is noted that the Modify PDURequest message (7816) sent by the AMF 218 to the SMF 220 and the ModifyPDU Response message (7818) sent by the SFM 220 to the AMF 218 start atstep (7812) and be performed in parallel with that and later steps.

The AMF 218 may send a Handover Request message (7820) to the T-RAN 204t. The message (7820) may include the Source to Target transparentcontainer, the MM N2 information, and the SM N2 info list). The AMF 218may determine and/or select the T-RAN 204 t based on the Target ID. TheAMF 218 may allocate a GUTI valid for the UE 202 in the AMF 218 andtarget TAI. The Source to Target transparent container may be forwardedas received from the S-RAN 204 s. The MM N2 information may include, forexample, security information and the Handover Restriction List. The SMN2 information list may include SM N2 information from the SMFs 220 inthe PDU Handover Response messages received until end of step (7814).

The T-RAN 204 t may send a Handover Request Acknowledge message (7822)to the AMF 218. The message (7822) may include the Target to Sourcetransparent container, the SM N2 response list, and the PDU sessionsfailed to be setup list. The Target to Source transparent container mayinclude a UE 202 container with an access stratum part and a NAS part.The UE 202 container may be sent transparently via the AMF 218 and theS-RAN 204 s to the UE 202. The information provided to the S-RAN 204 smay also include a list of PDU session IDs indicating the PDU sessionsthat failed to be setup and the reason for the failure (e.g., SMF 220decision, SMF 220 response too late, or T-RAN 204 t decision). The SM N2response list includes, per each received SM N2 information and by theSMF 220 accepted PDU session for N2 Handover, a PDU session ID and a SMN2 response indicating the PDU session ID and if T-RAN 204 t acceptedthe N2 Handover request for the PDU session. For each by T-RAN 204 taccepted PDU session for N2 Handover, the SM N2 response may include theN3 UP address and the Tunnel ID of the T-RAN 204 t, and the list ofaccepted QoS flows. For PDU sessions that the T-RAN 204 t rejects, theT-RAN 204 t may delete the PDU session contexts.

The AMF may send a Modify PDU Request message (7824) to the SMF 220. Themessage (7824) may include the PDU session ID, and the SM N2 response.For each T-RAN 204 t received SM N2 response (included in the SM N2response list), the AMF 218 may send the received SM N2 response to theSMF 220 indicated by the respective PDU Session ID.

The SMF 220 may send a Modify PDU Response message (7826) to the AMF218. The message (7826) may include the PDU session ID, and the message(7826) may be sent for each received Modify PDU Request message (7824).The SMF 220 may perform preparations for N2 Handover by indicating theN3 UP address and the Tunnel ID of T-RAN 204 t to the UPF 212 if the N2Handover is accepted by the T-RAN 204 t. If the N2 Handover is notaccepted by T-RAN 204 t, the SMF 212 may decides whether to release ordeactivate PDU session. For PDU session to be released, the SMFinitiates the PDU session release procedure described in Clause 4.3.4 ofTS 23.502 Version 0.3.0, published in March 2017. For the PDU sessionsto be deactivated, the SMF sends an N4 Session Modification Request tothe UPF for these PDU sessions. The message indicates the release of(R)AN N3 tunnel information ((R)AN Address and Tunnel EndpointIdentifier for the downlink user plane), Buffering Command, ReactivationTimer). The Buffering Command is to indicate whether the UPF shallbuffer the incoming downlink packets.

The Reactivation Timer indicates a duration that the UP of a deactivatedPDU session remains in deactivated state after the UPF removes the (R)ANN3 tunnel information. Before the Reactivation Timer expires, the UPFshall buffer the downlink packets according to the Buffering Command.After the Reactivation Timer expires, the UPF shall buffer the downlinkpackets according to the Buffering Command. If the UPF receives downlinkpacket before or after the Reactivation Timer expires, the UPF sendsdownlink packet notification to the SMF to initiate Network TriggeredService Request.

The SMF 220 acknowledges the Modify Request message (7824) by sending aModify PDU Response message (7826) to the AMF 218. For PDU sessions thatare deactivated, the message (7826) may include N1 SM Message Container(Session Deactivation Request (PDU Session ID(s), Reactivation Timer).The SMF stores the deactivation state of deactivated PDU session(s).

The AMF may send a Handover Command message (7828) to the S-RAN 204 s.The message (7828) may include the Target to Source transparentcontainer, the list of PDU sessions failed to be setup, and N1 SMMessage Container received in message (7826). The Target to Sourcetransparent container may be forwarded as received from the AMF 218. TheS-RAN 204 s may use the list of PDU sessions that failed to be setup andthe indicated reason for failure to determine whether or not to proceedwith the N2 Handover procedure.

The S-RAN 204 s may send a Handover Command message (7830) to the UE202. The message may include the UE 202 container and N1 SM MessageContainer. The UE 202 container may be sent transparently from the T-RAN204 t via the AMF 218 to the S-RAN 204 s and is provided to the UE 202by the S-RAN 204 s.

After the UE 202 has successfully synchronized (7832) to the targetcell, it may send the Handover Confirm message (7834) to the T-RAN 204t. The Handover is, by this message, considered by the UE 202 to besuccessful. The message may include N1 SM Acknowledgement (PDU SessionID(s)) for successfully switched and deactivated PDU sessions. Fordeactivated PDU sessions, the UE 202 stores the deactivated state of PDUsession(s). The UE 202 does not send an uplink request for aReactivation Timer. This timer can be set by a parameter in the UE 202policy or by a message from the SMF 220.

The T-RAN 204 t may next send to the AMF 218 a Handover Notify message(7838). The message (7838) may contain N1 SM Acknowledgment receivedfrom the UE in message (7834). The handover is, by this message,considered as successful in the T-RAN 204 t. The AMF 218 may then send aHandover Complete message (7840) to the SMF 220. The message may includethe PDU session ID and N1 SM Message from the UE 202. A HandoverComplete message (7840) may be sent per each PDU Session to thecorresponding SMF 220 to indicate the success of the N2 Handover.

The SMF 220 may send a Handover Complete ACK message (7842) to the AMF218. The message (7842) may include the PDU session ID. The SMF 220 mayindicate to the selected UPF 212 that the downlink User Plane for theindicated PDU session may be switched to the T-RAN 204 t. For PDUsessions that are not supported by the T-RAN 204 t and are deactivated,the SMF 220 may notify the selected UPF 212 to remove the (R)AN N3tunnel information, Reactivation Timer, and Buffering Command. The SMF220 may thus confirm reception of the Handover Complete message. The AMF218 may send to the S-RAN 204 s a UE Context Release Command ( ) message(7846). Next, the S-RAN 204 s may send to the AMF 218 a UE ContextRelease Complete 0 message (7848). The source (R)AN 204 s may releaseits resources related to the UE 202 and respond with the UE ContextRelease Complete ( ) message (7846).

UE or Network Requested PDU Session Release for Non-Roaming and Roamingwith Local Breakout.

FIG. 80 illustrates an example embodiment including both a UE requestedPDU session release procedure and a network requested PDU sessionrelease procedure. This procedure allows the UE to request the releaseof one PDU session. The procedure also allows the SMF or PCF to initiatethe release of a PDU session. In the case of LBO, the procedure is as inthe case of non-roaming with the difference that the SMF, the UPF andthe PCF are located in the visited network.

The procedure of FIG. 80 is triggered by one of the following options:

-   -   Step 8002 a: The UE initiates the UE requested PDU session        release procedure by the transmission of an N1 SM PDU Session        Release Request (PDU Session ID) message. The N1 message is        forwarded by the (R)AN to the 5G Core with an indication of User        Location Information. This message is relayed to the SMF        corresponding to the PDU Session ID via N2 and the AMF.        Depending on the access type, when the UE is in CM-IDLE state,        the UE can trigger a Service Request procedure before being able        to release the PDU session.    -   Step 8002 b: The PCF may initiate the PDU-CAN Session        modification procedure to request the release of the PDU        session.    -   Step 8002 c: The SMF may initiate release of a PDU session, for        example based on a request from the DN (cancelling the UE        authorization to access to the DN) or based on a request from        the UDM (subscription change) or from the OCS. The release        procedure also may be triggered based on locally configured        policy (e.g. the release procedure may be related with the UPF        relocation for SSC mode 2/mode 3).

When the SMF receives any one of the triggers in step 8002 a-8002 c, theSMF starts PDU session release procedure.

Step 8004: The SMF releases the IP address/Prefix(es) that wereallocated to the PDU session and releases the corresponding User Planeresources:

-   -   Step 8004 a: The SMF sends an N4 Session Release Request (N4        Session ID) message to the UPF. The UPF may drop any remaining        packets of the PDU session and release all tunnel resource and        contexts associated with the N4 Session.    -   Step 8004 b: The UPF acknowledges the N4 Session Release Request        by the transmission of an N4 Session Release Response (N4        Session ID) message to the SMF.

If there are multiple UPFs associated with the PDU session, the SessionRelease Request procedure (steps 8004 a and 8004 b) may be done for eachUPF.

Step 8006: The SMF sends an N11 Request message to the AMF (N2 SMResource Release request, N1 SM Information (PDU Session ReleaseCommand))

The SMF creates an N1 SM Information including PDU Session ReleaseCommand message (PDU Session ID, Cause). The Cause may indicate atrigger to establish a new PDU session with the same characteristics(e.g. when procedures related with SSC mode 2 are invoked).

SSC mode 2 is defined in clause 5.6.9. of TS 23.501

If the UP connection of the PDU session is active, the SMF shall alsocreate an N2 SM request to release the (R)AN resources associated withthe PDU session (N2 Resource Release request (PDU Session ID)).

If the PDU session is deactivated, the SMF may send a Session Releaseindication and PDU Session ID to the AMF.

The SMF sends an N11 message to the AMF (N2 SM Resource Release request,N1 SM Container (PDU Session Release Command), PDU Session ReleaseIndication, PDU Session ID) message to the AMF. The PDU Session ReleaseIndication tells the AMF about PDU session release notification. The AMFmay skip sending the N1 SM container to the UE when the UE is in CM-IDLEstate.

Step 8008: If the UE is in CM-IDLE state, the AMF may acknowledge thestep 8006 in step 8014; and steps 8008 to 8012 and 8016 may be skipped.

The UE and the 5GC will get synchronized about the status (released) ofthe PDU session at the next Service Request or Registration procedure.

If the UE is in CM-CONNECTED state, then the AMF transfers the messagereceived from the SMF in step 8006 (N2 SM Resource Release request, N1SM Information) message to the (R)AN.

Step 8010: If the (R)AN receives an N2 SM request to release the ANresources associated with the PDU session it issues AN specificsignalling exchange(s) with the UE to release the corresponding ANresources.

In case of a 3GPP RAN, an RRC Connection Reconfiguration may take placewith the UE releasing the RAN resources related to the PDU session.

During this procedure, the (R)AN sends any NAS message (N1 SM PDUSession Release Command) received from the AMF in step 8008. If the(R)AN receives only N1 SM Container (PDU Session Release Command), the(R)AN forwards this messages to the UE.

The UE acknowledges the PDU Session Release Command by sending a PDUSession Release Ack message via N1 SM signalling sent over the (R)AN.

Step 8012: [Conditional] If the (R)AN had received an N2 SM request torelease the AN resources, the (R)AN acknowledges the N2 SM ResourceRelease Request by sending an N2 SM Resource Release Ack (N1 SMInformation (PDU Session Release Ack), User Location Information)Message to the AMF. Otherwise, the (R)AN just forwards the N1 SMInformation (PDU Session Release Ack) from the UE to the AMF.

Step 8014: If the UE is in CM-CONNECTED state, the AMF sends N11Response message (an N2 SM Resource Release Ack) to forward the messagereceived from (R)AN in step 6 to the SMF. If the UE is in CM-IDLE state,the AMF sends to the SMF an N11 Response message (Session ReleaseAcknowledgment, PDU Session ID). The AMF may remove all contexts(including the PDU session ID) associated with the PDU session.

Step 8016: If the PDU session is activated, the SMF notifies the AMFthat the PDU session is released. The AMF and SMF may remove allcontexts (including the PDU session ID) associated with the PDU session.In some embodiments, this may take the form of an Nsmf PDU Session EventReport Notification (AMF): The SMF sends (N11 Message) PDU Session EventReport Notification as defined in Clause 5.2.8.1 to the AMF; the eventtrigger is PDU session release.

Step 8018: If Dynamic PCC applied to this session the SMF initiates thePDU-CAN session termination procedure. SMF notifies any entity that hassubscribed to User Location Information related with PDU session change.If it is the last PDU session it is handling for the UE the SMF releasesthe association with the UDM. The order with which SMF releases theresources is implementation dependant. If PDU session is deactivated,step 8018 can be performed in parallel, before or after step 8006.

Alternative Embodiments A

In alternative embodiments, steps 8006 through 8018 may operate asfollows:

Step 8006: The SMF sends an N11 message to the AMF (N2 SM PDU SessionRelease request, N1 SM PDU Session Release request, N11 PDU SessionRelease notification). The N1 SM PDU Session Release request includesPDU Session ID, Cause. The Cause may indicate a trigger to establish anew PDU session with the same characteristics (e.g. when proceduresrelated with SSC mode 2 are invoked).

SSC mode 2 is defined in TS 23.501[2] clause 5.6.9.

The N2 SM PDU Session Release request is to release the (R)AN resourcesassociated with the PDU session (N2 Resource Release request (PDUSession ID)). The N11 PDU Session Release notification includes PDUSession ID for the AMF to delete PDU session context.

If the UP of PDU session is activated, the SMF sends N1 SM PDU SessionRelease request and N2 SM PDU Session Release request via the AMF.

If the UP of PDU session is deactivated, and if the SMF does notsubscribe to the Namf_EventExpose service of AMF for UE CM statechanges, the SMF sends the N1 SM message to the UE via the AMF.

If the UP of PDU session is deactivated, and the SMF knows that the UEis in CM-IDLE state, the SMF sends N11 PDU Session Release request.Otherwise, if the SMF knows that the UE is in CM-CONNECTED state, theSMF sends N1 SM PDU Session Release Request.

In some embodiments, this may take the form a Namf Message Transfer(SMF): The SMF requests Namf Message Transfer service of the AMF definedin Clause 5.2.2.4 to sends N1 SM and N2 SM messages to the UE and (R)AN.

Step 8008: If the UE is in CM-IDLE state and N11 PDU Session Releasenotification is received, the AMF acknowledges the step 8006 in step8014; and steps 8008 to 8012 and 8016 are skipped. If the UE is inCM-IDLE state and the N1 SM message received, the AMF sends a deliveryreject in step 8014; steps 8008 to 8012 and 8016 are skipped.

The UE and the 5GC will get synchronized about the status (released) ofthe PDU session at the next Service Request or Registration procedure.

If the UE is in CM-CONNECTED state, then the AMF transfers the messagereceived from the SMF in step 3 (N2 SM PDU Session Release request, N1SM PDU Session Release request) message to the (R)AN.

8010: If the (R)AN receives an N2 SM PDU Session Release request torelease the AN resources associated with the PDU session it issues ANspecific signalling exchange(s) with the UE to release the correspondingAN resources. In case of a 3GPP RAN, an RRC Connection Reconfigurationmay take place with the UE releasing the RAN resources related to thePDU session. During this procedure, the (R)AN sends any NAS message (N1SM PDU Session Release Request) received from the AMF in step 8008.

If the (R)AN receives only N1 SM Container (PDU Session Releaserequest), the (R)AN forwards this messages to the UE. The UEacknowledges the PDU Session Release Request by sending a PDU SessionRelease Ack message via N1 SM signalling sent over the (R)AN.

8012: [Conditional] If the (R)AN had received an N2 SM request torelease the AN resources, the (R)AN acknowledges the N2 SM PDU SessionRelease Request by sending an N2 SM PDU Session Release Ack (N1 SMInformation (PDU Session Release Ack), User Location Information)Message to the AMF. Otherwise, the (R)AN just forwards the N1 SMInformation (PDU Session Release Ack) from the UE to the AMF.

8014: If the UE is in CM-CONNECTED state, the AMF sends N11 Responsemessage (an N2 SM PDU Session Release Ack) to forward the messagereceived from (R)AN in step 6 to the SMF. If the UE is in CM-IDLE stateand the AMF received N11 PDU Session Release notification in step 3, theAMF sends to the SMF an N11 Response message (PDU Session Releaseacknowledgment, PDU Session ID). If the UE is in CM-IDLE state and theAMF received N1 SM message in step 3, the AMF sends a delivery rejectmessage to the SMF indicating CM-IDLE state of the UE. The AMF and SMFmay remove all contexts (including the PDU session ID) associated withthe PDU session.

8016: If the PDU session is activated, the SMF sends N11 PDU SessionRelease notification to the AMF. The AMF and SMF may remove all contexts(including the PDU session ID) associated with the PDU session. In someembodiments, this may take the form of a Nsmf_PDU Session Event ReportNotification (AMF): The SMF sends (N11 Message) PDU Session Event ReportNotification as defined in Clause 5.2.8.1 to the AMF; the event triggeris PDU session release.

8018: If Dynamic PCC applied to this session the SMF initiates thePDU-CAN session termination procedure. SMF notifies any entity that hassubscribed to User Location Information related with PDU session change.If it is the last PDU session it is handling for the UE the SMF releasesthe association with the UDM. The order with which SMF releases theresources is implementation dependant. If PDU session is deactivated,step 8018 can be performed in parallel, before or after step 8006.

Alternative Embodiments B

In further alternative embodiments, steps 8006 through 8018 may operateas follows:

Step 8006: The SMF sends to the AMF N2 SM PDU Session Release request,N1 SM PDU Session Release request, N11 PDU Session Release notification.The N1 SM PDU Session Release request includes PDU Session ID, Cause.The Cause may indicate a trigger to establish a new PDU session with thesame characteristics (e.g. when procedures related with SSC mode 2 areinvoked). SSC mode 2 is defined in TS 23.501[2] clause 5.6.9.

The N2 SM PDU Session Release request is to release the (R)AN resourcesassociated with the PDU session (N2 Resource Release request (PDUSession ID)). The N11 PDU Session Release notification includes PDUSession ID for the AMF to delete PDU session context. If the UP of PDUsession is activated, the SMF sends N1 SM PDU Session Release requestand N2 SM PDU Session Release request. If the UE is unreachable, the SMFsends N11 PDU Session Release notification. If the UP of PDU session isdeactivated, the SMF sends the N1 SM PDU Session Release request.

In some embodiments, this may take the form a Namf Message Transfer(SMF): The SMF requests Namf_Message Transfer service of the AMF definedin Clause 5.2.2.4 to sends N1 SM and N2 SM messages to the UE and (R)AN.

Step 8008: If the UE is in CM-IDLE state and N1 SM message is received,the AMF drops the N1 SM message and acknowledges the step 8006 in step8014; and steps 8008 to 8012 are skipped. The UE and the 5GC will getsynchronized about the status (released) of the PDU session at the nextService Request or Registration procedure.

If the UE is in CM-CONNECTED state, then the AMF transfers the messagereceived from the SMF in step 3 (N2 SM PDU Session Release request, N1SM PDU Session Release request) message to the (R)AN.

Step 8010: When the (R)AN has received an N2 SM PDU Session Releaserequest to release the AN resources associated with the PDU session itissues AN specific signalling exchange(s) with the UE to release thecorresponding AN resources. In case of a 3GPP RAN, an RRC ConnectionReconfiguration may take place with the UE releasing the RAN resourcesrelated to the PDU session. During the this procedure, the (R)AN sendsany NAS message (N1 SM PDU Session Releaserequest) received from the AMFin step 8008.

If the (R)AN only receives N1 SM Container (PDU Session Releaserequest), the (R)AN forwards this message to the UE. The UE acknowledgesthe PDU Session Release request by sending a PDU Session Release Ackmessage via N1 SM signalling sent over the (R)AN.

Step 8012: [Conditional] If the (R)AN had received an N2 SM request torelease the AN resources, the (R)AN acknowledges the N2 SM PDU SessionRelease Request by sending an N2 SM PDU SessionRelease Ack (N1 SMInformation (PDU Session Release Ack), User Location Information)Message to the AMF. Otherwise, the (R)AN just forwards the N1 SMInformation (PDU Session Release Ack) from the UE to the AMF.

Step 8014: If the UE is in CM-CONNECTED state, the AMF sends N11Response message (an N2 SM PDU SessionRelease Ack) to forward themessage received from (R)AN in step 6 to the SMF.

If the AMF received N11 PDU Session Release notification in step 8006,the AMF sends to the SMF an N11 Response message (PDU Session Releaseacknowledgment, PDU Session ID), and step 8016 is skipped. The AMF andSMF may remove all contexts (including the PDU session ID) associatedwith the PDU session.

If the SBA message is used, the N11 Response message (PDU SessionRelease acknowledgment, PDU Session ID) may be not required.

If the UE is in CM-IDLE state and the AMF received N1 SM message in step8006, the AMF sends a delivery reject message to the SMF with a causecode indicating CM-IDLE state of the UE. This is particularly applicableto cases in which the process is started via either of steps 8002 b or8002 c.

Step 8016: The SMF sends N11 PDU Session Release notification to theAMF. The AMF and SMF may remove all contexts (including the PDU sessionID) associated with the PDU session. In some embodiments, this may takethe form of a Nsmf_PDU Session Event Report Notification (AMF): The SMFsends (N11 Message) PDU Session Event Report Notification as defined inClause 5.2.8.1 to the AMF; the event trigger is PDU session release.

Step 8018: If Dynamic PCC applied to this session the SMF initiates thePDU-CAN session termination procedure. SMF notifies any entity that hassubscribed to User Location Information related with PDU session change.If it is the last PDU session it is handling for the UE, the SMFreleases the association with the UDM. The order with which SMF releasesthe resources is implementation dependant. If PDU session is deactivatedand the SMF knows the CM state, step 8018 can be performed in parallel,before or after step 8006.

Alternative Embodiment C

In further alternative embodiments, steps 8006 through 8018 may operateas follows:

Step 8006: The SMF sends to the AMF (N2 SM Resource Release request, N1SM Information). The N1 SM Information includes PDU Session ReleaseCommand message (PDU Session ID, Cause. The Cause may indicate a triggerto establish a new PDU session with the same characteristics (e.g. whenprocedures related with SSC mode 2 are invoked). The SSC mode 2 isdefined in TS 23.501, clause 5.6.9. The N2 SM Resource Release request(PDU Session ID) is to release the (R)AN resources associated with thePDU session.

If the UP of PDU session is activated, the SMF sends N1 SM PDU SessionRelease Command and N2 SM Resource Release request by invokingNamf_Communication_N1MessageTransfer andNamf_Communication_N2MessageTrigger service operations respectively.

If the UP of PDU session is deactivated, the SMF requests the UE torelease the PDU session by invokingNamf_Communication_N1MessageTransfer(N1 SM message(PDU Session ReleaseCommand), Skip Indication). If the UE is in CM-IDLE state and the AMFreceives N1 SM message with Skip Indication, the AMF drops the N1 SMmessage and notifies the SMF “Message Not Transferred with a causecode”; Steps 8008 to 8014 are skipped. The “Skip Indication” is optionaland described in clause 5.2.2.2.7 of TS 23.502.

If the UE is unreachable, the SMF notifies the AMF that the PDU sessionis released by invoking the Nsmf_EventExposure_Notify (PDU SessionRelease indication, PDU Session ID). The AMF and SMF shall remove allcontexts (including the PDU session ID) associated with the PDU sessionas well as any event subscriptions by the SMF on the AMF. Steps 8008 to8016 are skipped.

If the procedure is triggered to relocate PDU session anchor of a PDUsession with SSC mode 2, the SMF is assumed not to include the “SkipIndication”.

The UE and the 5GC will get synchronized about the status (released) ofthe PDU session at the next Service Request or Registration procedure.

Step 8008: If the UE is in CM-IDLE state and “Skip Indication” is notreceived, the AMF initiates the network triggered Service Requestprocedure to transmit the N1 SM Information to the UE.

If the UE is in CM-CONNECTED state, then the AMF transfers the messagereceived from the SMF in step 3 (N2 SM Resource Release request, N1 SMInformation) message to the (R)AN.

Step 8010: When the (R)AN has received an N2 SM request to release theAN resources associated with the PDU session it issues AN specificsignalling exchange(s) with the UE to release the corresponding ANresources.

In case of a 3GPP RAN, an RRC Connection Reconfiguration may take placewith the UE releasing the RAN resources related to the PDU session.

During this procedure, the (R)AN sends any NAS message (N1 SM PDUSession Release Command) received from the AMF in step 8008.

The UE acknowledges the PDU Session Release Command by sending a PDUSession Release Ack message via N1 SM signalling sent over the (R)AN.

Step 8012. [Conditional] If the (R)AN had received an N2 SM request torelease the AN resources, the (R)AN acknowledges the N2 SM ResourceRelease Request by sending an N2 SM Resource Release Ack (N1 SMInformation (PDU Session Release Ack), User Location Information)Message to the AMF.

Otherwise, the (R)AN just forwards the N1 SM Information (PDU SessionRelease Ack) from the UE to the AMF.

Step 8014: The AMF invokes the Namf_Communication_N1MessageNotify(N1 SMRelease Ack) as defined in clause 5.2.2.2.4 of TS 23.502 to the SMF. TheAMF invokes the Namf_Communication_N2InfoNotify (N2 SM Resource ReleaseAck) as defined in clause 5.2.2.2.11 of TS 23.502 to the SMF.

Step 8016: The SMF notifies the AMF that the PDU session is released byinvoking the Nsmf_EventExposure_Notify service operation as defined inclause 5.2.8.3.2 of TS 23.502. The AMF and SMF shall remove all contexts(including the PDU session ID) associated with the PDU session as wellas any event subscriptions by the SMF on the AMF.

Step 8018: If Dynamic PCC applied to this session the SMF initiates thePDU-CAN session termination procedure. The SMF notifies any entity thathas subscribed to User Location Information related with PDU sessionchange. If it is the last PDU session it is handling for the UE the SMFreleases the association with the UDM. The order with which SMF releasesthe resources is implementation dependant. If PDU session is deactivatedand the SMF knows the CM state, step 9 can be performed in parallel,before or after step 3.

In the alternative embodiment C, theNamf_Communication_N1MessageTransfer service operation is described asfollows.

Service operation name: Namf_Communication_N1MessageTransfer.

Description: CN NF request to transfer downlink N1 message to the UEthrough the AMF.

Known NF Consumers: SMF, SMSF, PCF, NEF

Inputs, Required: CN NF ID, Message Container (s)

Inputs, Optional: One subscribe Indication on whether the transferringcreates a temporary binding on the AMF for later notification ofresponse message. “Skip Indication” indicates that the AMF shall skipsending the N1 SM container to the UE if the UE is in CM-IDLE state.

Outputs, Required: Result indication includes “Transferred” and “NotTransferred with cause”.

Outputs, Optional: None.

See step 10 of clause 4.3.2.2.1, step 14 of clause 4.3.2.2.2 and step 5aof clause 4.13.3.6 for details of this service operation. If the AMFdoes not have a N1 context for the UE and if the UE is in CM-IDLE state,the AMF initiates the network triggered service request procedure asspecified in clause 4.2.3.4. The AMF responds to the consumer NF, with aNamf_Communication_N1MessageTransfer response, providing a resultindication of whether the AMF was able to successfully transfer the N1message towards the UE.

In some embodiments, an explicit subscription(Namf_Communication_N1MessageSubscribe) for the N1 response message typemay piggyback Namf_Communication_N1MessageTransfer service operationinvocation.

Avoid Storing PDU Session State in AMF and Update Related Procedures

In some procedures of TS 23.502, such as UE Context release in the ANand Handover procedures, it is assumed that the AMF stores the PDUsession state (activated or deactivated). However, this assumptionviolates the AMF and SMF separation principle. Alternative solutionsthat do not require the knowledge of PDU session state at the AMF aredescribed below.

Clause 5.2.2.3 of TS 23.502 defines that the AMF provides and “EventExposure” service. Accordingly, the SMF may subscribe to this service ifthe SMF serves at least one PDU session of a specific RAT. The SMF cansubscribe to this service even if all of PDU sessions it serves aredeactivated. Regarding UE Context Release in the AN procedure, the SMFcan subscribe to “Event Exposure” triggered by CM state change fromCONNECTED to IDLE state when the UE request session establishment orsession activation. Then the AMF just needs to notifies the SMF about CMstate transitioning to CM-IDLE, to the subscribed SMF. It is up to SMFto decide suitable actions.

The SMF may subscribe to “Namf_EventExposure” service of the AMF inSession Establishment and Service Request procedures.

The SMF may subscribed to “Namf_Communication_N2InfoSubscribe” serviceof the AMF as defined in clause 5.2.2.2.9 of TS 23.502 in order to getnotified about the N2 UE Context Release Request from the (R)AN to AMF.The SMF performs “Namf_Communication_N2InfoSubscribe” service operationin the Session Establishment and Service Request procedures.

In the Service Request procedures in TS 23.502, the AMF may reject theservice activation request. It is also possible that the (R)AN may nothave resources to serve the PDU session, in which case the (R)AN mayalso reject the PDU session establishment request. In order to implementthis functionality, the procedures defined in TS 23.502 may be revisedas follows:

Clause 4.3.2.2.1 Non-Roaming and Roaming with Local Breakout

Step 16. SMF to AMF: SM response (Cause).

After this step, the AMF forwards relevant events to the SMF, forexample at handover where the (R)AN Tunnel Info changes or the AMF isrelocated.

The SMF may subscribe to Namf_EventExposure service of the AMF (UE ID,event filter) as defined in clause 5.2.2.3. The event filter is “CMstate change to CM-IDLE”.

The SMF may subscribe to N2 messages of type SM and “N2 UE ContextRelease Request” using the Namf_Communication_N2InfoSubscribe serviceoperation of the AMF as defined in clause 5.2.2.2.9.

Clause 4.3.2.2.2 Home-Routed Roaming

Step 20. This step is the same as step 16 in clause 4.3.2.2.1. with thefollowing differences:

-   -   The SMF is a V-SMF

Clause 4.2.6 UE Context Release in the AN

This procedure is used to release the logical N2-AP signallingconnection and the associated N3 User Plane connections.

When the N2-AP signalling connection is lost due to (R)AN or AMFfailure, the UE context release in the AN procedure is performed locallyby the AMF or the (R)AN as described in the procedure flow below withoutusing or relying on any of the signalling shown between (R)AN and AMF.The UE context release in the AN causes all PDU sessions of the UE to bedeactivated.

The initiation of UE context release in the AN procedure may be due to:

-   -   (R)AN-initiated with cause e.g. O&M Intervention, Unspecified        Failure, AN (e.g. Radio) Link Failure, User Inactivity, Release        due to UE generated signalling connection release, etc; or    -   AMF-initiated with cause e.g. Unspecified Failure, etc.

Both (R)AN-initiated and AMF-initiated UE context release in the ANprocedures are shown in FIG. 81. Referring to the figure:

Step 8102: If there is some confirmed AN conditions (e.g. Radio LinkFailure) or for other (R)AN internal reason, the (R)AN may decide toinitiate the UE context release in the AN. In this case, the (R)AN sendsa N2 UE Context Release Request (Cause) message to the AMF. Causeindicates the reason for the release (e.g. AN Link Failure, O&Mintervention, unspecified failure, etc.). The decision to initiate a UEcontext release in the AN Procedure may also be triggered by an internalAMF event

Step 8104: [Conditional] For each of the SMF serving PDU sessions thatsubscribed to Namf_EventExposure_Subscribe, the AMF performsNamf_EventExposure_Notify as described in clause 5.2.2.3.4. In someembodiments, the (R)AN information may be used in cases in which the UEhas multiple connections. Alternatively, the mobility event containermay contain a list of PDU Session ID(s).

Alternative Embodiment of Step 8104

Step 8104 a: [Conditional] For each of the SMF serving PDU sessions thatsubscribed to Namf_Communication_N2InfoSubscribe for N2 Information Type“N2 UE Context Release Request” the AMF performsNamf_Comunication_N2InfoNotify service operation as described in clause5.2.2.2.11 to notify PDU session Id, Release Cause(N2 UE Context ReleaseRequest).

The AMF may send (R)AN information to the SMF in case the UE hasmultiple connections. Alternatively, the AMF may send the list of PDUSession ID(s).

Step 8104 b: [Conditional] The SMF sends to the AMF a response to themessage received in Step 8104 a.

Step 8106 a: [Conditional] SMF to UPF: N4 Session Modification Request(AN tunnel info to be removed, Buffering on/off). The SMF initiates a N4Session Modification procedure indicating the need to remove AN TunnelInfo. Buffering on/off indicates whether the UPF may buffer incoming DLPDU or not. See clause 4.4 for more details.

Step 8106 b: [Conditional] UPF to SMF: N4 Session Modification Responseacknowledging the SMF request. See clause 4.4 for more details.

Step 8108 a: the SMF sends N2 Context Release Command to the AMF viaNamf_Communication_N2MessageTrigger service operation as defined inclause 5.2.2.2.8 of TS 23.502.

Step 8108 b: The AMF sends a response message for Step 8108 a.

Step 8108 c. The SMF may perform Namf_Communication_N2InfoUnsubscribefor specific N2 Information Type, such as N2 UE Context Release Request,as defined in clause 5.2.2.2.10 of TS 23.502.

Step 8108 d: [Conditional] The SMF may performNamf_EventExposureUnSubscribe procedure for some types of UE mobilityevents as defined in clause 5.2.2.3.3 of TS 23.502.

Step 8110: After the AMF collects all the N2 Context Release Command instep 4 from the SMF(s) that were notified in Step 2, the AMF sends tothe (R)AN a N2 UE Context Release Request. In case the AN is a RAN thisstep is described in detail in RAN specifications. In case the AN is aN3IWF this step is described in clause 4.12.

This step may be performed before, in parallel with, or after step 8104,as desired.

Step 8112: If the AN connection (e.g. RRC connection) with the UE is notalready released (step 8102), the (R)AN requests the UE to release theAN connection. Upon receiving AN connection release confirmation fromthe UE, the (R)AN deletes the UE's context.

Step 8114: The (R)AN confirms the N2 Release by returning an N2 UEContext Release Complete ( ) message to the AMF. With this, thesignalling connection between the AMF and the (R)AN for that UE isreleased.

During the procedure of FIG. 81, the AN may provide location informationto the AMF.

Clause 4.2.3.2 UE Triggered Service Request in CM-IDLE State

FIGS. 82A and 82B illustrate an example procedure for UE triggeredService Request in CM-IDLE state. This example procedure also includesaspects required to support network slicing.

The Service Request procedure may be used by a 5G UE in CM-IDLE state torequest the establishment of a secure connection to an AMF. The UE inCM-IDLE state initiates the Service Request procedure in order to senduplink signalling messages, user data, or response to a network pagingrequest. After receiving the Service Request message, the AMF mayperform authentication, and the AMF may perform the security procedure.After the establishment of a secure signalling connection to an AMF, theUE or network may send signalling messages, e.g. PDU sessionestablishment from UE to the network, or the SMF, via the AMF, may startthe User Plane resource establishment for the PDU sessions requested bynetwork and/or indicated in the Service Request message.

For any Service Request, the AMF may respond with a Service Responsemessage to synchronize PDU session status between UE and network. TheAMF may also respond with Service Reject message to UE, if the ServiceRequest cannot be accepted by network. For Service Request due to userdata, the network may take further actions if User Plane resourceestablishment is not successful.

The procedure in this clause 4.2.3.2 is applicable to the scenarios withor without intermediate UPF, and with or without intermediate UPFreselection.

The procedure defined in clause 4.2.3.2 of TS 23.502 is not applicablefor an access network (once the UE is registered in the network) inwhich the UE is always considered as in CM-CONNECTED state and in whichthe User Plane resource is always considered established for an activePDU session.

Referring to FIGS. 82A and 82B:

Step 8202: UE to (R)AN: MM NAS Service Request (PDU session ID(s),security parameters, PDU session status). The UE sends NAS messageService Request towards the AMF encapsulated in an RRC message to theRAN. The RRC message(s) that can be used to carry the 5G Temporary IDand this NAS message are described in RAN specifications. If the ServiceRequest is triggered for user data, the UE includes the PDU sessionID(s) in NAS Service Request message to indicate the PDU session(s) thatthe UE needs to use. If the Service Request is triggered for signallingonly, the UE doesn't include any PDU session ID. When this procedure istriggered for paging response, if the UE needs to use some PDUsession(s), the UE includes the PDU session ID(s) in MM NAS ServiceRequest message to indicate the PDU session(s) that the UE needs to use.Otherwise the UE will not include any PDU session ID. The PDU sessionstatus indicates the PDU sessions available in the UE. In someembodiments, the NAS Service Request may also include an indication ofuser data, signalling or paging response.

Step 8204: (R)AN to AMF: N2 Message (MM NAS Service Request, 5GTemporary ID, Location information, RAT type, RRC establishment cause).Details of this step are described in RAN specifications. If the AMFcan't handle the Service Request it will reject it. 5G Temporary ID isobtained in RRC procedure. RAN selects the AMF according to TemporaryID. The Location Information and RAT type relates to the cell in whichthe UE is camping. Based on the PDU session status, the AMF may initiatePDU session release procedure if the PDU session is not available in theUE.

Step 8206: If the Service Request was not sent integrity protected orintegrity protection is indicated as failed, the AMF may initiate NASauthentication/security procedure as defined in clause 4.6. If the UEtriggered the Service Request to establish a signalling connection only,after the security exchange the UE and the network can send signallingand steps 8208 and 8214 to 8224 are skipped.

Step 8208: [Conditional] AMF to SMF: N11 Message (PDU session ID(s),Cause(s), UE location information). The N11 message is sent in one ormore of the following scenarios:

-   -   If the MM NAS Service Request message includes PDU session        ID(s), or this procedure is triggered by SMF but PDU session IDs        from UE correlates to other SMFs than the one triggering the        procedure, the AMF sends N11 message to SMF(s) associated with        the PDU session ID(s) with Cause set to indicate “establishment        of user plane resources” for a PDU session.    -   If the UE was in MICO mode and the AMF had notified an SMF of        the UE being unreachable and that SMF needs not send DL data        notifications to the AMF, the AMF informs the SMF that the UE is        reachable.

The AMF may also notify any other NF that subscribed to UE reachabilitythat the UE is reachable.

Step 8210: Based on the new location info, the SMF checks the UPFSelection Criteria according to clause 6.3.3 of TS 23.501 [2], anddetermines to perform one of the following:

-   -   continue using the current UPF(s);    -   select a new intermediate UPF, if the UE has moved out of the        service area of UPF that is connecting to RAN, while maintaining        the UPF(s) acting as PDU Session Anchor; or    -   trigger re-establishment of the PDU Session to perform        relocation of the UPF acting as PDU Session anchor.

Step 8212 a: [Conditional] SMF to new UPF: N4 Session EstablishmentRequest. If the SMF selects a new UPF to act as intermediate UPF for thePDU session, an N4 Session Establishment Request message is sent to thenew UPF, providing Packet detection, enforcement and reporting rules tobe installed on the intermediate UPF. The PDU session anchor info forthis PDU Session is also provided to the intermediate UPF.

Step 8212 b: New UPF (intermediate) to SMF: N4 Session EstablishmentResponse. The new intermediate UPF sends an N4 Session EstablishmentResponse message to the SMF. In case the UPF allocates CN tunnel info,it provides CN DL tunnel info and UL tunnel info (i.e. CN N3 tunnelinfo) to the SMF. The SMF starts a timer, to be used in step 17a torelease the resource in old intermediate UPF if there is one.

Step 8214 a: [Conditional] SMF to UPF (PSA): N4 Session ModificationRequest. If the SMF selects a new UPF to act as intermediate UPF for thePDU session, the SMF sends N4 Session Modification Request message toPDU session anchor UPF, UPF (PSA), providing the DL tunnel informationfrom new intermediate UPF.

Step 8214 b: UPF (PSA) to SMF: N4 Session Modification Response. The UPF(PSA) sends N4 Session Modification Response message to SMF.

Step 8216: [Conditional] SMF to AMF: N11 Message (N1 SM information (PDUsession ID, PDU Session re-establishment indication), N2 SM information(PDU Session ID, QoS profile, CN N3 Tunnel Info, S-NSSAI)) to the AMF.Upon reception of the N11 Message in 4 with cause including“establishment of user plane resources”, the SMF determines whether UPFreallocation is performed, based on the UE location information, UPFservice area and operator policies:

-   -   For PDU session that SMF determines to be served by the current        PDU Session Anchor UPF in step 8210, the SMF generates only N2        SM information and sends N11 Message to the AMF to establish the        User Plane(s). The N2 SM information contains information that        the AMF may provide to the RAN.    -   For PDU sessions that SMF determines that UPF reallocation for        PDU Session Anchor UPF is needed in step 8210, SMF may send N11        Message containing only N1 SM information to UE via AMF. The N1        SM information includes the corresponding PDU session ID and PDU        Session re-establishment indication, which is the same as step 2        described in clause 4.3.5.1.1 of TS 23.501[2].

Upon reception of the N11 Message in step 8208 with an indication thatthe UE is reachable, if the SMF has pending DL data the SMF sends N11Message to the AMF to establish the User Plane(s) for the PDU sessions,otherwise the SMF resumes sending DL data notifications to the AMF incase of DL data.

Step 8218: AMF to (R)AN: N2 Request (N2 SM information received fromSMF, security context, AMF Signalling Connection ID, HandoverRestriction List, MM NAS Service Accept). RAN stores the SecurityContext, AMF Signalling Connection Id, QoS Information for the QoS Flowsof the PDU Sessions that are activated and N3 Tunnel IDs in the UE RANcontext. The step is described in detail in RAN specifications. HandoverRestriction List is described in TS 23.501 [2] clause 5.3.4.1 “MobilityRestrictions”. MM NAS Service Accept includes PDU session status in AMF.If N1 SM information is received from step 8, the Service Accept messagealso includes N1 SM information. AMF may include at least one N2 SMinformation from SMF if the procedure is triggered for PDU session UserPlane setup. AMF may send additional N2 SM information from SMFs inseparate N2 message(s) (e.g. N2 tunnel setup request), if there is any.Alternatively, if multiple SMFs are involved, the AMF may send one N2Request message to (R)AN after all the N11 messages from SMFs arereceived. In such case, the N2 Request message includes the N2 SMinformation received in each of the N11 messages and information toenable AMF to associate responses to relevant SMF.

Step 8220: (R)AN to UE: The RAN performs RRC Connection Reconfigurationwith the UE depending on the QoS Information for all the QoS Flows ofthe PDU Sessions activated and Data Radio Bearers. The User Planesecurity is established at this step, which is described in detail inRAN specifications. The RAN forwards the MM NAS Service Accept to theUE. The UE locally deletes context of PDU sessions that are notavailable in 5G CN. If the N1 message is present in the Service Acceptand indicates that the any PDU session needs to be re-established, theUE initiates PDU session re-establishment after Service Requestprocedure is complete. That is, for SSC mode 2, step 3 and step 4 isdefined in clause 4.3.5.1.1 is performed. For SSC mode 3, step 3 and 4defined in clause 4.3.5.2 is performed.

Step 8222: After the User Plane radio resources are setup, the uplinkdata from the UE can now be forwarded to RAN. The 5G RAN sends theuplink data to the UPF address and Tunnel ID provided in the step 4.

Step 8224: [Conditional] (R)AN to AMF: N2 Request Ack (N2 SM information(RAN Tunnel info, List of accepted QoS Flows for the PDU Sessionsactivated, List of rejected QoS Flows for the PDU Sessions activated).This step is described in detail in RAN specifications. The message mayinclude N2 SM information(s), e.g. RAN tunnel information. RAN mayrespond N2 SM information with separate N2 message (e.g. N2 tunnel setupresponse) if AMF sends separate N2 message in step 8210. If multiple N2SM information are included in the N2 Request message in step 8210, theN2 Request Ack includes multiple N2 SM information and information toenable the AMF to associate the responses to relevant SMF.

Step 8226: [Conditional] AMF to SMF: N11 Message (N2 SM information (RANTunnel info), RAT Type) per accepted PDU Session to the SMF. If the AMFreceived N2 SM information (one or multiple) in step 8, then the AMF mayforward the N2 SM information to the relevant SMF. If the UE Time Zonehas changed compared to the last reported UE Time Zone then the AMF mayinclude the UE Time Zone IE in this message.

Step 8228: [Optional] SMF to PCF: If dynamic PCC is deployed, SMF mayinitiate IP-CAN Session Modification and provides new locationinformation to the PCF. Step 8230 a: [Conditional] SMF to newintermediate UPF: N4 Session Modification Request (RAN tunnel info). Ifthe SMF selected a new UPF to act as intermediate UPF for the PDUsession in step 5, SMF initiates a N4 Session Modification procedure andprovides RAN Tunnel Info.

Step 8230 b: [Conditional] UPF to SMF: N4 Session Update Response.

Step 8232 a: [Conditional] The SMF may performNamf_Communication_N2InfoSubscribe service operation as defined inclause 5.2.2.2.9 for N2 Information Type “N2 UE Context ReleaseRequest”.

Step 8232 b: [Conditional] The SMF may performNamf_EventExpose_Subscribe procedure as defined in clause 5.2.2.3.2 forcertain UE mobility events. If desired, this step may be performedtogether with step 8216.

Step 8234 a: [Conditional] SMF to old intermediate UPF: N4 SessionModification Request or N4 Session Release Request. If the SMF decidedto continue using the old intermediate UPF in step 5, the SMF sends anN4 Session Modification Request, providing (R)AN tunnel information. Ifthe SMF decided to select a new UPF to act as intermediate UPF, the SMFinitiates resource release, after timer in step 8212 b expires, bysending an N4 Session Release Request (Release Cause) to the oldintermediate UPF. If there is no intermediate UPF, the SMF sends an N4Session Modification Request to the PSA UPF, providing (R)AN tunnelinformation.

Step 8234 b: Old intermediate UPF to SMF: N4 Session ModificationResponse or N4 Session Release Response. The old UPF acknowledges withan N4 Session Modification Response or N4 Session Release Responsemessage to confirm the modification or release of resources. If there isno intermediate UPF, the PSA UPF sends an N4 Session ModificationResponse to the SMF to confirm the modification of resources.

Clause 4.2.3.3 UE Triggered Service Request in CM-CONNECTED State

FIGS. 83A and 83B illustrate an example procedure for UE triggeredService Request in CM-IDLE state. This example procedure also includesaspects required to support network slicing.

The network may take further actions if User Plane resourceestablishment is not successful.

The procedure in this clause 4.2.3.3 is applicable to the scenarios withor without intermediate UPF, and with or without intermediate UPFreselection.

The procedure in this clause 4.2.3.3 TS 23.502 is not applicable for anaccess network (once the UE is registered in the network) in which theUE is always considered as in CM-CONNECTED state and in which the UserPlane resource is always considered established for an active PDUsession.

Referring to FIGS. 83A and 83B:

Step 8302: UE to (R)AN: MM NAS Service Request (PDU session ID(s)). TheUE sends NAS message Service Request towards the AMF encapsulated in anRRC message to the RAN. The MM NAS Service Request message may beencrypted and integrity protected. The PDU session ID(s) in NAS messageService Request message indicates the PDU session that the UE selects toactivate.

Step 8304: (R)AN to AMF: N2 Message (MM NAS Service Request). Details ofthis step are described in RAN specifications. If the Service Requestcannot be handled by the AMF, the AMF reject it. The (R)AN forwards theMM NAS Service Request message to the AMF based on the existing N2connection.

Step 8306: [Conditional] AMF to SMF: N11 Message (PDU session ID(s)).The AMF sends N11 message to SMF(s) associated with the PDU sessionID(s).

Step 8308: Based on the new location info, the SMF checks the UPFSelection Criteria according to clause 6.3.3 of TS 23.501 [2]. If the UEhas moved out of the service area of UPF that is connecting the UE tothe RAN, the SMF may select a new intermediate UPF.

Step 8310 a: [Conditional] SMF to new intermediate UPF: N4 SessionEstablishment Request, If the SMF selects a new intermediate UPF for thePDU session, an N4 Session Establishment Request message is sent to thenew intermediate UPF, providing Packet detection, enforcement andreporting rules to be installed on the T-UPF. The PDU session anchorinfo for this PDU Session is also provided to the T-UPF.

Step 8310 b: New UPF to SMF: N4 Session Establishment Response. The newUPF sends an N4 Session Establishment Response message to the SMF. Ifthe UPF allocates CN tunnel info, the UPF provides CN DL tunnel info andUL tunnel info (i.e. CN N3 tunnel info) to the SMF. The SMF starts atimer, to be used in step 8417 a to release the resource in old UPF ifthere is one.

Step 8312 a: [Conditional] SMF to UPF (PSA): N4 Session ModificationRequest. If the SMF selects a new UPF to act as intermediate UPF for thePDU session, the SMF sends N4 Session Modification Request message toPDU session anchor UPF, UPF (PSA), providing the DL tunnel informationfor the new intermediate UPF.

Step 8312 b: UPF (PSA) to SMF: N4 Session Modification Response. The UPF(PSA) sends N4 Session Modification Response message to SMF.

Step 8314: [Conditional]SMF to AMF: N11 Message (N2 SM information (PDUSession ID, QoS profile, CN N3 Tunnel Info, S-NSSAI)) to the AMF The SMFgenerates N2 SM information and sends N11 Message to the AMF toestablish the User Plane(s) for the PDU sessions. The N2 SM informationcontains information that the AMF may provide to the RAN.

Step 8316: [Conditional]AMF to (R)AN: N2 Request (N2 SM information (QoSprofile, CN N3 Tunnel Info) received from SMF, MM NAS Service Accept).If there are multiple PDU Sessions that involves multiple SMFs, AMF doesnot need wait for responses from all SMFs in step 8306 b.

Step 8318: (R)AN to UE: The RAN performs RRC Connection Reconfigurationwith the UE depending on the QoS Information for all the QoS Flows ofthe PDU Sessions and Data Radio Bearers activated. The RAN forwards theMM NAS Service Accept to the UE.

Step 8320: After the User Plane radio resources for the selected PDUsession are setup, the uplink data from the UE can now be forwarded toRAN. The 5G RAN sends the uplink data to the UPF address and Tunnel IDprovided in the step 8314.

Step 8322: [Conditional] (R)AN to AMF: N2 Request Ack (N2 SM information(RAN Tunnel info, List of accepted QoS Flows for the PDU Sessionsactivated, List of rejected QoS Flows for the PDU Sessions activated).This step is described in detail in RAN specifications. The message mayinclude N2 SM information(s), e.g. RAN tunnel information. RAN mayrespond N2 SM information with separate N2 message (e.g. N2 tunnel setupresponse).

Step 8324: [Conditional] AMF to SMF: N11 Message (N2 SM information (RANTunnel info, List of accepted QoS Flows, List of rejected QoS Flows))per accepted PDU Session to the SMF.

Step 8326: [Optional] SMF to PCF: If dynamic PCC is deployed, SMF mayinitiate IP-CAN Session Modification and provides new locationinformation to the PCF.

Step 8328 a: [Conditional] SMF to UPF: N4 Session Update Request (RANtunnel info and List of accepted QoS Flows). If the SMF selects a newUPF to act as intermediate UPF for the PDU session in step 4, the SMFinitiates a N4 Session Modification procedure and provides RAN TunnelInfo.

Step 8328 b: [Conditional] UPF to SMF: N4 Session Update Response.

Step 8330 a: [Conditional] The SMF performsNamf_Communication_N2InfoSubscribe service operation as defined inclause 5.2.2.2.9 for N2 Information Type “N2 UE Context ReleaseRequest”.

Step 8330 b: [Conditional] The SMF may performNamf_EventExpose_Subscribe procedure as defined in clause 5.2.2.3.2 forcertain UE mobility events. This step may be performed together withstep 8314.

Step 8332 a: [Conditional] SMF to old UPF (intermediate): N4 SessionModification Request or N4 Session Release Request. If the SMF decidedto continue using the old intermediate UPF in step 4, the SMF sends anN4 Session Modification Request, providing (R)AN tunnel information. Ifthe SMF decided to select a new UPF to act as intermediate UPF in Step8308, the SMF initiates resource release, after timer in step 8312 bexpires, by sending an N4 Session Release Request (Release Cause) to oldintermediate UPF. If there is no intermediate UPF, the SMF sends an N4Session Modification Request to the PSA UPF, providing (R)AN tunnelinformation.

Step 8332 b: Old UPF (intermediate) to SMF: N4 Session ModificationResponse or N4 Session Release Response. The old UPF (intermediate)acknowledges with an N4 Session Release Response message to confirm themodification or release of resources. If there is no intermediate UPF,the PSA UPF sends an N4 Session Modification Response to the SMF toconfirm the modification of resources.

Based on the foregoing, it will be appreciated that aspects of thepresent inventon provide any one or more of:

-   -   A method of releasing a packet data unit (PDU) session, the        method comprising:        -   determining to trigger a PDU session release;        -   sending a N4 Session Release Request message to a User Plane            Function (UPF);        -   receiving a N4 Session Release Response message from the            UPF;        -   sending a N11 Request with PDU Session Release Command to an            access and mobility function (AMF);        -   receiving a N11 Response with PDU Session Release            Acknowledgement from the AMF; and        -   sending a N11 message to the AMF.    -   A handover method, the method comprising:        -   receiving a N2 Path Switch Request from a Target Radio            Access Network (T-RAN);        -   sending a N11 Message to a Session Management Function            (SMF);        -   receiving N11 Message Acknowledgment from the SMF; and        -   sending a N2 Path Switch Request Acknowledgment to the            T-RAN.

Although the present invention has been described with reference tospecific features and embodiments thereof, it is evident that variousmodifications and combinations can be made thereto without departingfrom the invention. The specification and drawings are, accordingly, tobe regarded simply as an illustration of the invention as defined by theappended claims, and are contemplated to cover any and allmodifications, variations, combinations or equivalents that fall withinthe scope of the present invention.

Unless defined otherwise, all technical and scientific terms used hereinhave the same meaning as commonly understood by one of ordinary skill inthe art to which this invention belongs.

Through the descriptions of the preceding embodiments, the presentinvention may be implemented by using hardware only or by using softwareand a necessary universal hardware platform. Based on suchunderstandings, the technical solution of the present invention may beembodied in the form of a software product. The software product may bestored in a non-volatile or non-transitory storage medium, which can bea compact disk read-only memory (CD-ROM), USB flash disk, or a removablehard disk. The software product includes a number of instructions thatenable a computer device (personal computer, server, or network device)to execute the methods provided in the embodiments of the presentinvention. For example, such an execution may correspond to a simulationof the logical operations as described herein. The software product mayadditionally or alternatively include number of instructions that enablea computer device to execute operations for configuring or programming adigital logic apparatus in accordance with embodiments of the presentinvention.

We claim:
 1. A method of releasing a N2 connection associated with auser equipment (UE), the method comprising: receiving, by an access andmobility management function (AMF) from an access network (AN), amessage including packet data unit (PDU) session identifiers (IDs)associated with PDU sessions of the UE; sending, by the AMF to a sessionmanagement function (SMF), a PDU session deactivation request todeactivate a PDU session, the PDU session deactivation request includingan identifier indicating the PDU session; receiving, by the AMF from theSMF, a PDU session deactivation response associated with the PDU sessiondeactivation request; indicating, by the AMF, to the AN to release a UEcontext of the UE after receiving the PDU session deactivation response;receiving, by the AMF from the AN, a confirmation of releasing the UEcontext; and releasing, by the AMF, the N2 connection associated withthe UE.
 2. The method of claim 1, wherein the message received by theAMF further includes a cause code.
 3. The method of claim 2, wherein thecause code indicates UE inactivity.
 4. The method of claim 2, whereinthe PDU session deactivation request includes the cause code.
 5. Themethod of claim 1, wherein the session deactivation request includes anotification of release of the N2 connection.
 6. The method of claim 1,wherein the PDU session IDs have an active N3 user plane.
 7. The methodof claim 1, wherein sending the PDU session deactivation requestcomprises: sending, by the AMF, multiple PDU session deactivationrequests to one or more SMFs, each of the multiple PDU sessiondeactivation requests including an identifier indicating a correspondingPDU session; and wherein receiving the PDU session deactivation responsecomprises: receiving, by the AMF from each of the one or more SMFs, oneor more PDU session deactivation responses each of which is a responseto a corresponding received one of the PDU session deactivationrequests.
 8. The method of claim 7, wherein the AMF indicates to the ANto release the UE context after receiving all the responses associatedwith the PDU session deactivation requests that the AMF has sent.
 9. Anetwork function comprising: at least one processor; and anon-transitory computer readable storage medium including instructionsconfigured to control the at least one processor to implement steps of:receiving, from an access network (AN), a message including packet dataunit (PDU) session identifiers (IDs) associated with PDU sessions of auser equipment (UE); sending, to a session management function (SMF), aPDU session deactivation request to deactivate a PDU session, the PDUsession deactivation request including an identifier indicating the PDUsession; receiving, from the SMF, a PDU session deactivation responseassociated with the PDU session deactivation request; indicating to theAN to release a UE context of the UE after receiving the PDU sessiondeactivation response; receiving, from the AN, a confirmation ofreleasing the UE context; and releasing a N2 connection associated withthe UE.
 10. The network function according to claim 9, wherein themessage received by the network function further includes a cause code.11. The network function according to claim 10, wherein the cause codeindicates UE inactivity.
 12. The network function according to claim 10,wherein the PDU session deactivation request includes the cause code.13. The network function according to claim 9, wherein the sessiondeactivation request includes a notification of release of the N2connection.
 14. The network function according to claim 9, wherein thePDU session IDs have an active N3 user plane.
 15. The network functionaccording to claim 9, wherein sending the PDU session deactivationrequest comprises: sending multiple PDU session deactivation requests toone or more SMFs, each of the multiple PDU session deactivation requestsincluding an identifier indicating a corresponding PDU session; andwherein receiving the PDU session deactivation response comprises:receiving, from each of the one or more SMFs, one or more PDU sessiondeactivation responses each of which is a response to a correspondingreceived one of the PDU session deactivation requests.
 16. The networkfunction according to claim 15, further configured to: monitor forreceipt of the PDU session deactivation responses from the one or moreSMFs; and trigger indicating to the AN to release the UE context uponreceipt of all the PDU session deactivation responses associated withthe PDU session deactivation requests that the network function hassent.
 17. A access network (AN) apparatus comprising: at least oneprocessor; and a non-transitory computer readable storage mediumincluding instructions configured to control the at least one processorto implement steps of: sending, to an access and mobility managementfunction (AMF), a message including packet data unit (PDU) sessionidentifiers (IDs) associated with PDU sessions of a user equipment (UE),the message is to trigger a deactivation of the PDU sessions; inresponse of the message, receiving, from the AMF, an indicationindicating to release a UE context of the UE; sending, to the AMF, aconfirmation of releasing the UE context; and releasing a N2 connectionassociated with the UE.
 18. The AN apparatus according to claim 17,wherein the message sent to the AMF further includes a cause code. 19.The AN apparatus according to claim 18, wherein the cause code indicatesUE inactivity.
 20. The AN apparatus according to claim 17, wherein theindication is received when one or more of the PDU sessions isdeactivated.